Related
I rooted my Unlocked xl 2 using a method I found online. Used it a couple of days rooted and decided to go back to stock so....
I downloaded the factory image, ran the flash -all.bat and everything was good. Next I went back to my boot loader to re lock it, ran the command , selected yes.
After I hit yes to re lock the boot loader I got the following error. COULD NOT FIND A VALID OPERATING SYSTEM.
Any help would be greatly appreciated.
skullymullins said:
I rooted my Unlocked xl 2 using a method I found online. Used it a couple of days rooted and decided to go back to stock so....
I downloaded the factory image, ran the flash -all.bat and everything was good. Next I went back to my boot loader to re lock it, ran the command , selected yes.
After I hit yes to re lock the boot loader I got the following error. COULD NOT FIND A VALID OPERATING SYSTEM.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
1. fastboot flashing unlock
2. fastboot flashing unlock_critical
3. Reboot the phone if prompted
4. flash firmware using flash-all script again. Read the results and watch for errors that might explain the problem and which partition (a or b) it is flashing to.
5. fastboot --set-active=b (or a. Just set it to whichever partition the script was not flashing to.)
6. flash firmware with flash-all script again to flash the alternate partition
Ok Thanks Ill give that a try..
skullymullins said:
Ok Thanks Ill give that a try..
Click to expand...
Click to collapse
And don't relock until you are 100 percent certain it is ok. I suggest waiting until you get the next update to be sure. Actually I suggest not relocking it but if you insist then wait and make sure the next update goes ok.
TonikJDK said:
And don't relock until you are 100 percent certain it is ok. I suggest waiting until you get the next update to be sure. Actually I suggest not relocking it but if you insist then wait and make sure the next update goes ok.
Click to expand...
Click to collapse
When I tried the command . fastboot --set-active b i got the unknown command error
skullymullins said:
When I tried the command . fastboot --set-active b i got the unknown command error
Click to expand...
Click to collapse
You rooted your phone with a method you found online??? Hmmmm, that's curious. Hope that didn't do any internal damage. Anyways, when your in fastboot mode, and type in "fastboot devices" do you get your device ID number??
TheSt33v said:
1. fastboot flashing unlock
2. fastboot flashing unlock_critical
3. Reboot the phone if prompted
4. flash firmware using flash-all script again. Read the results and watch for errors that might explain the problem and which partition (a or b) it is flashing to.
5. fastboot --set-active b (or a. Just set it to whichever partition the script was not flashing to.)
6. flash firmware with flash-all script again to flash the alternate partition
Click to expand...
Click to collapse
I told one person that was having trouble also to instead of doing step 4 instead download Deuces bootloop kit and allow it to flash your phone for you because I noticed a few people were not flashing in fastboot properly the pixel is different from the prior phones they are used to there are many more Sig files that were not all getting flashed thoroughly causing issues. Deuces kit does it all perfect and it's pretty easy to set up and go
skullymullins said:
When I tried the command . fastboot --set-active b i got the unknown command error
Click to expand...
Click to collapse
Maybe that command works also. I use
Fastboot --set-active=b
skullymullins said:
When I tried the command . fastboot --set-active b i got the unknown command error
Click to expand...
Click to collapse
Sorry, the previous post is right. You need an = in there.
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Shadowsalyer said:
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Click to expand...
Click to collapse
small chance you enable root from developer options. (i think it will be adb only)
if so , maybe can use adb shell and "dd" to write recovery to correct partition.
problem is many of the available twrp do not boot on custom rom .
example code. (if you do wrong , it may be bad)
Code:
dd if=/ext_sdcard/twrp_Recovery_ramdisk.img of=/dev/block/mmcblk0p32
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Shadowsalyer said:
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Click to expand...
Click to collapse
Like what you have , twrp stuck on splash screen
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Shadowsalyer said:
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Click to expand...
Click to collapse
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Just to clarify, it gets stuck on TWRP splash screen. When I turn off the phone, it immediately boots up again into TWRP. I tried getting into fastboot mode with all kinds of combinations of button presses, but no luck. Not even Volume Up + USB cable works
smokinjoe2122 said:
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
I have seen this happen before , solution was to wait for dead battery, or disassemble to unplug battery
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
This is because after the frp unlock, it needed to see a factory reset, and it usually needs to be done with stock recvery.
So will have to wait till battery is dead and and plug in usb while holding volume button. Should then load to fastboot. Where it is best to flash stock recovery to clear the recovery bootloop. The bootloop is do to the fact yo unlocked frp and now phone needs to wipe/data
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
dcraffam said:
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
Click to expand...
Click to collapse
i just took mine apart and discconected the battery and still no luck that program deleted my fastboot
Please can you tell me the process to install twrp I have the L24
I waited all the way till the battery drained, stuck in the USB, and it booted to ROM! Sadly it immediately shut off again because the battery is dead (even with keeping the USB in). I'm going to keep trying though.
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Shadowsalyer said:
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Click to expand...
Click to collapse
Seems to be a f-up situation either way.
You have adb DD available, found out before.
Don't know if maybe flashing stock recovery is good idea at this point.
I think fastboot.img can be flashed with DD too, but don't try till someone can confirm.
If flash stock recovery clears the loops, maybe best to do full-ota manual flashing.
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Shadowsalyer said:
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Click to expand...
Click to collapse
Fastboot.img is the large part the bootloader. If flashing it goes bad, might be dead phone after, just rember that.
Will add a list of partition names and command s for you soon.
here is a list of oreo partitions and there /dev/blk/** number
and here is an example of code to save images with dd assuming you put the images on your extrnal-sdcard in folder called oreo-images
Code:
dd if=/dev/block/mmcblk0p5 of=/mnt/ext_sdcard/oreo-images/fastboot.img
Do that save first and compare the md5 of the file from update.app to this file.
or just check the md5 before making the copy
Code:
adb shell md5sum /dev/block/mmcblk0p5
If you are conviced you need to flash the images, here is example of writing the image assuming files are in sdcard folder oreo-update-images
Code:
dd if=/mnt/ext_sdcard/oreoupdate-images/fastboot.img of=/dev/block/mmcblk0p5
As I have said, this might be bad advise , I have not done fastboot.img flashing before. But on other devices it is same as lk.img or uboot.img, There is danger in flashing it incorrectly. That is why my suggestion was to flash no-check-recovery and do manael update with "echo -update_package" commands.
Along with the statement that fastboot.img is similar to lk.img or uboot.img on other phones, Your fastboot cannot be gone. because phone boots.
but do let us know how it goes.
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Shadowsalyer said:
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Click to expand...
Click to collapse
To recovery_ramdisk. 32
What about check md5 of fastboot partition, that will be helpful to know if it did get wiped out.?
Hmm seems like I'm not allowed to use dd after all:
HWBND-H:/ $ dd if=/storage/7C96-7E17/BND-RECOVERY-NoCheck.img of=/dev/block/mmcblk0p32
dd: /dev/block/mmcblk0p32: Permission denied
And here I was thinking I was close to solving it...
Also can't run md5sum on the fastboot partition, since that needs root as well.
Stuck on boot logo !!!!! :crying:
Can't :
1. Can't boot to ROM (as doing so just stays on boot logo)
2. Can't boot into recovery (as doing this gets me to either black screen or just boots back to the boot logo)
Can :
1. Can enter bootloader
2. Can able to use fastboot commands
Tried:
1. flashing stock ROM several times,
2. flashing stock recovery
3. flashing twrp recovery
:crying:
Check my guide. It might come handy.
https://forum.xda-developers.com/le...-lenovo-p2-t4006405/post80955105#post80955105
alirazaagha said:
Check my guide. It might come handy.
https://forum.xda-developers.com/le...-lenovo-p2-t4006405/post80955105#post80955105
Click to expand...
Click to collapse
Friend thanks for the reply but your link just says "Duplicate thread. "
hackiee said:
Friend thanks for the reply but your link just says "Duplicate thread. "
Click to expand...
Click to collapse
Yes, it was. Check this one.
https://forum.xda-developers.com/lenovo-p2/how-to/guide-unbrick-unlocked-lenovo-p2-t4006401
alirazaagha said:
Yes, it was. Check this one.
https://forum.xda-developers.com/lenovo-p2/how-to/guide-unbrick-unlocked-lenovo-p2-t4006401
Click to expand...
Click to collapse
Thanks for your post friend, but, your guide doesn't fulfill my situation.
As, I am stuck on bootliader or boot logo.
I have flashed all firmwares s048,s233,s244,s51 through fastboot but none of them able to get me out of it.
Even tried flashing various recoveries both stock and twrp but neither of them helped
If, anyhow I can be able to enter into TWRP. It will solve the problem. But, I don't know nothing seems to work.
Even tried corrupting the bootloader and then flashing blankflash, but that too didn't able to get me out of the bootlogo.
Please help ?
alirazaagha said:
Yes, it was. Check this one.
https://forum.xda-developers.com/lenovo-p2/how-to/guide-unbrick-unlocked-lenovo-p2-t4006401
Click to expand...
Click to collapse
Hey, can you please do 1 thing.
Can you provide an image of the bootloader mode of your lenovo p2, if, there's something to lookup idk
I am attaching image of my bootloader, if you can look into it.
Thanks
hackiee said:
Hey, can you please do 1 thing.
Can you provide an image of the bootloader mode of your lenovo p2, if, there's something to lookup idk
I am attaching image of my bootloader, if you can look into it.
Thanks
Click to expand...
Click to collapse
It's alright.
alirazaagha said:
It's alright.
Click to expand...
Click to collapse
nothing strange ? Ok thanks
hackiee said:
nothing strange ? Ok thanks
Click to expand...
Click to collapse
Yep. Go ahead. You can try S244 firmware to try and boot your phone. If it boots then update accordingly as I mentioned in my guide.
alirazaagha said:
Yep. Go ahead. You can try S244 firmware to try and boot your phone. If it boots then update accordingly as I mentioned in my guide.
Click to expand...
Click to collapse
Still no luck! :crying: flashed S244 several times but nothing.
Can you confirm one more thing.
When I give
"Fastboot format system" I get :
"Formatting is not supported for file system with type 'raw'."
screenshot attached. Please check
hackiee said:
Still no luck! :crying: flashed S244 several times but nothing.
Can you confirm one more thing.
When I give
"Fastboot format system" I get :
"Formatting is not supported for file system with type 'raw'."
screenshot attached. Please check
Click to expand...
Click to collapse
OK so you are not following my guide Check .txt file attached in that guide and if you are still unsure then ask me.
alirazaagha said:
OK so you are not following my guide Check .txt file attached in that guide and if you are still unsure then ask me.
Click to expand...
Click to collapse
I have checked the text file of your guide, and they are the same instructions which I have been following since start. :silly:
The "fastboot format system" is a command which I used to do on my Moto G, and was able to format system successfully.
But, I don't remember if it used to work on P2 or not , that's why I asked you. If, you can use that command to check the output on your device.
Thanks
hackiee said:
I have checked the text file of your guide, and they are the same instructions which I have been following since start. :silly:
The "fastboot format system" is a command which I used to do on my Moto G, and was able to format system successfully.
But, I don't remember if it used to work on P2 or not , that's why I asked you. If, you can use that command to check the output on your device.
Thanks
Click to expand...
Click to collapse
Hmmm so you haven't read .txt file carefully. Command is:
Fastboot ERASE system
See the difference now? :silly:
Please, discuss it on that thread if need so others could also benefit from it.
alirazaagha said:
Hmmm so you haven't read .txt file carefully. Command is:
Fastboot ERASE system.
Click to expand...
Click to collapse
OMG, yes brother, I already know the command, and I have used it several times, the fastboot ERASE command, but, as mentioned several timesin the past, it is not solving my problem.
As, I am still not able to enter into any recovery(neither stock nor twrp), and not able to boot and OS.
That's why, I wanna try "Fastboot format system" command.
If, somehow that solves my problem
hackiee said:
OMG, yes brother, I already know the command, and I have used it several times, the fastboot ERASE command, but, as mentioned several timesin the past, it is not solving my problem.
As, I am still not able to enter into any recovery(neither stock nor twrp), and not able to boot and OS.
That's why, I wanna try "Fastboot format system" command.
If, somehow that solves my problem
Click to expand...
Click to collapse
OK. I though that you only tried Format command not erase. You should skip this command and do the whole process. I have added this command so that previous system files are erased. But, I booted my phone without using this command first time. Second time, I tried to see if I can do it all in a single process then I added this command and it worked without any issues and all the process went smooth and phone booted like a new one.
Try all commands but skip erase system command.
stuck on logo , have access to fastboot only
My phone stuck on logo when i open it or when i insert charger
when i try to open recovery(volume up + down) it turned off and i can't open recovery by any way
i can access fastboot
i tried your instruction and Lenovo+P2+UnBrick+OneTeam-EypCnn and all other fastboot roms
i tried install Twrp and stock recovery
i tried blankflash
that didn't help ,i can only access fastboot
what is your recommendation ? it's a hardware issue ?
DrGhost001 said:
stuck on logo , have access to fastboot only
My phone stuck on logo when i open it or when i insert charger
when i try to open recovery(volume up + down) it turned off and i can't open recovery by any way
i can access fastboot
i tried your instruction and Lenovo+P2+UnBrick+OneTeam-EypCnn and all other fastboot roms
i tried install Twrp and stock recovery
i tried blankflash
that didn't help ,i can only access fastboot
what is your recommendation ? it's a hardware issue ?
Click to expand...
Click to collapse
Did you find any solution?
Same issue here, I guess it's a hardware issue: SSD is damaged ?
fastboot erase system
fastboot format:ext4 system
Maybe related to the file system ?
i have the same probelm, do you guys find any solution ?
Is there a way i can recover my data ? I need to recover my kid's graduation pictures. I will pay for help if I need too.
I was rooted and using 11.2.4.4.LE15AA. I uninstalled Magisk then i tried updating to 11.2.5.5 via ota , it kept saying install failed i need to reboot and now I'm stuck in fastboot.
edit: and now it doesn't turn off.
Im a flipping idiot.
Thanks in advance.
https://mega.nz/file/7YQj3SIR#5yDfje2mVgPVRdZi-gYrDRvvQE2hx_DYD00vicZH8Fo
This is a zip from one of the top 3 pinned threads on this OP9P forum that has stock and patched boot.img from your 4.4AA build..(if thats what ur phone is still on). U may be able to download the zip, put on ur pc, extract it, then open cmd and fastboot boot (then drag the stock boot.img to the command prompt u typed in) and hit enter.. It may work to get u back booted unrooted...
Shooter7889 said:
https://mega.nz/file/7YQj3SIR#5yDfje2mVgPVRdZi-gYrDRvvQE2hx_DYD00vicZH8Fo
This is a zip from one of the top 3 pinned threads on this OP9P forum that has stock and patched boot.img from your 4.4AA build..(if thats what ur phone is still on). U may be able to download the zip, put on ur pc, extract it, then open cmd and fastboot boot (then drag the stock boot.img to the command prompt u typed in) and hit enter.. It may work to get u back booted unrooted...
Click to expand...
Click to collapse
Crap that didn't work. I'm so beyond screwed. I wonder IF and when TWRP comes out if I will be able to decrypt then.
Try flashing 4.4 or 5.5 full OTA via fastboot/fastbootd. If you are gonna try the 5.5 then you gotta use EU/India.
TWRP at this point is a pipe dream. Decrypt doesn't even work for A10 on OP and Android is moving faster than TWRP can keep up.
craznazn said:
Try flashing 4.4 or 5.5 full OTA via fastboot/fastbootd. If you are gonna try the 5.5 then you gotta use EU/India.
TWRP at this point is a pipe dream. Decrypt doesn't even work for A10 on OP and Android is moving faster than TWRP can keep up.
Click to expand...
Click to collapse
Is that where i flash all the individual .imgs with fastboot? or just system.img
Individual
In case this comes from magisk modules, just try to reboot in safe mode:
Safe Mode
1. Hold power until it goes off
2. Boot and wait for the bootloader warning
3. Hold vol up and down until boot animation
4. Once it's booted just reboot again and you're done
Now on boot all magisk modules are disabled
Other option, have you try to flash your original boot!
craznazn said:
Individual
Click to expand...
Click to collapse
I get this for several of the img files.
FAILED (remote: Flashing is not allowed for Critical Partitions
But I'm able to get to recovery now, with this error
boot reason fs_mgr_mount_all
Fastbootd for critical partitions (not fastboot)
I wiped it.
close the thread.
Oh too bad i had your solution, as ihad the same problem last week.
For anyone else in this situation you have to flash the stock boot img to opposite partition. Then boot to that partition. Get your data off at that point before you do anything else. Then try to re-root
Please post the method utilized for to KEEP data when new OTA available and have a custom kernel such as Eng.stk's Blu_spark.
The problem I ran into today was an unstable recovery experience, no desktop connection as ADB sideload was going to be my method to retain data. This eventually led me to an android laying on back black screen "error!" or "No Command".
I got back to fastboot, and did a flash_all.bat procedure via Windows.
OR ,can't we restore stock kernel and update system on settings page? I tried last time for JAN when I tried reflashing the same boot.img from the update I was on using fastboot flash boot (boot.img) didn't work I couldn't post. SO I flash_all.bat in fastboot.
How can we take the OTA.zip and apply it.
use pixel flasher to flash the full image and then flash then custom kernel
Edit the flash-all.sh to replace the "-w" parameter with "--skip-reboot" on the last real line to prevent it from wiping userdata and remain in fastboot. Then install your custom images like "fastboot flash boot boot.img". Then finally "fastboot reboot".
Isn't removing the -w parameter the way to let it not ''wipe'' everything? Had something similar this week in the end recovered via the android flash tool and ticked off the wipe data parameters then when it booted again applied root again after that the costum rom(in my case kikura which can't be flashed using fastboot)
96carboard said:
Edit the flash-all.sh to replace the "-w" parameter with "--skip-reboot" on the last real line to prevent it from wiping userdata and remain in fastboot. Then install your custom images like "fastboot flash boot boot.img". Then finally "fastboot reboot".
Click to expand...
Click to collapse
I wouldn't mess with that lol Thats my last resort of flashing do you know anything about applying an OTA.zip not the flash_all.bat
You know Google hoping things wont be derped after they bring up a second fastboot fastboot'd. XD
kingpeppermint said:
Isn't removing the -w parameter the way to let it not ''wipe'' everything? Had something similar this week in the end recovered via the android flash tool and ticked off the wipe data parameters then when it booted again applied root again after that the costum rom(in my case kikura which can't be flashed using fastboot)
Click to expand...
Click to collapse
Why do you think I said to replace it with the parameter to prevent it from rebooting?
Stoowyguy said:
I wouldn't mess with that lol Thats my last resort of flashing do you know anything about applying an OTA.zip not the flash_all.bat
Click to expand...
Click to collapse
I guess you like doing things the dangerous way, huh?