So I have of course verified that my device is still unlocked. I have tried every method I can think of with no results of bringing this phone back to life. Anyways...
I can use flashall.bat of any version and everything looks all swell until you try to boot. Either it gets stuck at fastboot or continues to boot up then restart before ever completing boot (Depends on the firmware I use)
I can still boot into twrp with fastboot boot twrp.img however flashing in there doesnt seem to help either.
I have tried the fbmode clear stuff already.
When I try to go to do a blank flash I issue the command fastboot oem blankflash
I get back:
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.010s
Also just so you dont think its locked or something..
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot oem unlock
...
(bootloader) Already unlocked
OKAY [ 0.010s]
finished. total time: 0.010s
Can anyone please help me its been months, haha.
Thank you
I am currently on the TMO March 2019 xt1789-04
Try issuing 'fastboot -w' w/o quotes in bootloader mode. That should format your data in case there was something leftover from other flashings.
41rw4lk said:
Try issuing 'fastboot -w' w/o quotes in bootloader mode. That should format your data in case there was something leftover from other flashings.
Click to expand...
Click to collapse
Unfortunately that does not solve the issue.
All I can think of is to reflash stock, maybe flash it twice and make sure you get both slots.
I have done both of those countless times with no success. I am not new to the phone either, I have flashed it back to stock when it was working countless times with no problem. Ive tried different cables different PCs and even the same pc it originally worked with, no luck.
Maybe try flashing DU and see if it'll boot. If you can get it to boot then do a quick setup, enable adb, then 'adb reboot edl' and blankflash it.
41rw4lk said:
Maybe try flashing DU and see if it'll boot. If you can get it to boot then do a quick setup, enable adb, then 'adb reboot edl' and blankflash it.
Click to expand...
Click to collapse
What is DU? I apologize, I am either spacing on it or have never heard the acronym before
H411UCIN093NIC said:
What is DU? I apologize, I am either spacing on it or have never heard the acronym before
Click to expand...
Click to collapse
Dirty Unicorns 13.3 pie based rom. It's pretty solid and what I currently use.
41rw4lk said:
Dirty Unicorns 13.3 pie based rom. It's pretty solid and what I currently use.
Click to expand...
Click to collapse
I cant even get stock to run. However I was able to bump my phone into EDM with the newest TWRP. After using blankflash I lost my ability to flash GPT partition. I cant even boot twrp anymore (.
I dont know what to do anymore.
H411UCIN093NIC said:
I cant even get stock to run. However I was able to bump my phone into EDM with the newest TWRP. After using blankflash I lost my ability to flash GPT partition. I cant even boot twrp anymore (.
I dont know what to do anymore.
Click to expand...
Click to collapse
I know you can't run stock, that's why I suggested trying to run DU. What steps did you take in twrp to get into EDL mode? I assume you're in bootloader, try to reboot the bootloader 1st to get a fresh session. 'fastboot reboot bootloader'
Then run 'fastboot getvar all' and verify that you're still unlocked. If all is good there, try flashing the latest stock firmware. If you can't get anything done there, try using the lmsa tool to rescue your device.
H411UCIN093NIC said:
I cant even get stock to run. However I was able to bump my phone into EDM with the newest TWRP. After using blankflash I lost my ability to flash GPT partition. I cant even boot twrp anymore (.
I dont know what to do anymore.
Click to expand...
Click to collapse
GPT isn't a partition. It is your partition table. If you can't set your partition table, you might have screwed up your eMMC.
https://en.m.wikipedia.org/wiki/GUID_Partition_Table
Uzephi said:
GPT isn't a partition. It is your partition table. If you can't set your partition table, you might have screwed up your eMMC.
https://en.m.wikipedia.org/wiki/GUID_Partition_Table
Click to expand...
Click to collapse
Alright so I have a better understanding of the symptoms of my device now. So it seems that there is an issue with Slot A. It often seems tedious even getting twrp to boot from img after a flashall in slot A. In slot B it loads on the first try. When I have twrp loaded on both slots I can go into the reboot menu and pick EDL. But here is the weird part, it will only boot into EDL if I am in slot B not slot A.
Also Lsma doesnt recognize my device as the current model, I also tried with all the varients.
So as GPT being a partitioning table, I would have assumed from flashing linux however I wasnt sure if android used a partition actually named gpt since in the flashall it said it was to flash a file called gpt but the file name was invalid. I guess it was named that for organizational purposes, sorry for the mixup.
Uzephi said:
GPT isn't a partition. It is your partition table. If you can't set your partition table, you might have screwed up your eMMC.
https://en.m.wikipedia.org/wiki/GUID_Partition_Table
Click to expand...
Click to collapse
EDL mode was achieved in slot A however blankflash is unable to be applied(only while in slot A)
This is my output:
C:\Users\Panda Vurze\Desktop\blankflash_from_NDX26.183-15_17>.\qboot.exe blank-flash
Motorola qboot utility version 3.85
[ 0.000] Opening device: \\.\COM7
[ 0.001] Detecting device
[ 34.039] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.039] Check qboot_log.txt for more details
[ 34.040] Total time: 34.042s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
H411UCIN093NIC said:
Alright so I have a better understanding of the symptoms of my device now. So it seems that there is an issue with Slot A. It often seems tedious even getting twrp to boot from img after a flashall in slot A. In slot B it loads on the first try. When I have twrp loaded on both slots I can go into the reboot menu and pick EDL. But here is the weird part, it will only boot into EDL if I am in slot B not slot A.
Also Lsma doesnt recognize my device as the current model, I also tried with all the varients.
So as GPT being a partitioning table, I would have assumed from flashing linux however I wasnt sure if android used a partition actually named gpt since in the flashall it said it was to flash a file called gpt but the file name was invalid. I guess it was named that for organizational purposes, sorry for the mixup.
Click to expand...
Click to collapse
You're a TMO variant right? I have a flashall that will flash both slots. So you can take not the newest flash all, but maybe 27.1.4 or so and flash it to both slots and when you boot you should be able to take an ota and get your slots back to a normal config where one slot is a build behind.
*Uzephi made the flashall originally, I should give him credit. I think they switched to standard flashall to keep thing copacetic, but nevertheless this one is both slots.
41rw4lk said:
You're a TMO variant right? I have a flashall that will flash both slots. So you can take not the newest flash all, but maybe 27.1.4 or so and flash it to both slots and when you boot you should be able to take an ota and get your slots back to a normal config where one slot is a build behind.
Click to expand...
Click to collapse
May I have the flashall or a paste of the internal .bat?
<3
I am totally TMO varient.
H411UCIN093NIC said:
May I have the flashall or a paste of the internal .bat?
<3
I am totally TMO varient.
Click to expand...
Click to collapse
My bad, I thought I added it but I didn't. It's there now.
41rw4lk said:
My bad, I thought I added it but I didn't. It's there now.
Click to expand...
Click to collapse
You said 27.1.4
I apologize if I am ignorant to that format for the firmware. What does that translate to in terms of the OTX27.(whatever comes next)
EDIT: Duh I see what you mean by posts in threads.
I see the 27.1.3 is that one ok too??
Uzephi said:
GPT isn't a partition. It is your partition table. If you can't set your partition table, you might have screwed up your eMMC.
https://en.m.wikipedia.org/wiki/GUID_Partition_Table
Click to expand...
Click to collapse
Just a shout out and personal thank you for the flashall. THANK YOUUU!!!! <33333
H411UCIN093NIC said:
You said 27.1.4
I apologize if I am ignorant to that format for the firmware. What does that translate to in terms of the OTX27.(whatever comes next)
EDIT: Duh I see what you mean by posts in threads.
I see the 27.1.3 is that one ok too??
Click to expand...
Click to collapse
Yeah that's fine, the idea is just to get to a point where you can take an ota so your slots will be all proper and you're good to go no matter how you proceed.
Related
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
ls2power said:
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
Click to expand...
Click to collapse
I just did a factory reset and it fixed it. I also was stock without twrp though.
seshaz said:
I just did a factory reset and it fixed it. I also was stock without twrp though.
Click to expand...
Click to collapse
I tried factory reset already but still shows system using 19.9gbs.
Have you tried doing a complete full flash of nde63v without installing TWRP or root to see if it goes back to normal?
cambunch said:
Have you tried doing a complete full flash of nde63v without installing TWRP or root to see if it goes back to normal?
Click to expand...
Click to collapse
yes i did a few times, it would just bootloop. Until i sideloaded ota nde63v on top of full system img then it booted fine
ls2power said:
I tried factory reset already but still shows system using 19.9gbs.
Click to expand...
Click to collapse
Mine shows system using 19.9 gigs also. I posted this on another thread as I thought it seemed high but no one said weather it was high or was not so I assumed it was normal to use 19.9 gigs of space on my verizon pixel xl. I"am rooted on the x software but I couldnt get twrp working and I figured what good was TWRP if there was no supersu that was working with it and I decided to wait for TWRP to get out of beta to try again.
ls2power said:
yes i did a few times, it would just bootloop. Until i sideloaded ota nde63v on top of full system img then it booted fine
Click to expand...
Click to collapse
If you are getting a bootloop after flashing a factory image, I would assume it isn't flashing correctly. Can you post the output of what happens when you run the flashall.bat?
cambunch said:
If you are getting a bootloop after factory a factory image, I would assume it isn't flashing correctly. Can you post the output of what happens when you run the flashall.bat?
Click to expand...
Click to collapse
im able to flash every single img, but when i try to flash flashall.bat it doesnt seem to work. I will give it a try once i get home from work. The only thing bugging me is that the system shows using 19.9gb of space.
Mine is only using 6.79GB. Something is definitely off with yours.
Sent from my Pixel XL using XDA-Developers mobile app
Neomage84 said:
Mine is only using 6.79GB. Something is definitely off with yours.
Click to expand...
Click to collapse
yes there is. When you reboot your phone, which slot does it have? And do you have twrp installed and root?
M9guy said:
Mine shows system using 19.9 gigs also. I posted this on another thread as I thought it seemed high but no one said weather it was high or was not so I assumed it was normal to use 19.9 gigs of space on my verizon pixel xl. I"am rooted on the x software but I couldnt get twrp working and I figured what good was TWRP if there was no supersu that was working with it and I decided to wait for TWRP to get out of beta to try again.
Click to expand...
Click to collapse
I fixed it, i flashed full system image while i was on slot A. Now system is using 5.39gb, im on V build.
i have the same problem with a 128GB version not sure whats up but to fix it i just flashed over and over and one of them just worked would be nice to know the cause so i dont have to flash many times to get it to show full space again.
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
theycallmerayj said:
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
Click to expand...
Click to collapse
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
theycallmerayj said:
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
Click to expand...
Click to collapse
theycallmerayj said:
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
Click to expand...
Click to collapse
whenever you flash a factory img or an OTA, or any firmware, the slots will switch unless told not to, i believe this is to keep them in sync aka the seamless updates. here is some info on that - http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
Quick Tip - while in cmdlne for ADB and Fastboot, and fully updated, just type
Code:
adb
to get all the ADB commands available, and likewise for fastboot, just type
Code:
fastboot
And to switch active slots type
Code:
fastboot set_active -a
or
Code:
fastboot set_active -b
. Then to activate slot
Code:
fastboot reboot bootloader
I believe with TWRP installed you have to switch slots in TWRP.
Click to expand...
Click to collapse
Moving on, I found this to be pretty helpful, it's not the exact answer you are looking for, but i think it will come in handy.
All dual-booting credit in this thread goes to hucqym, this wasn't my idea, im just a messenger.
hucqym said:
so I successfully have the dual boot running on my pixel (verizon edition) with the same configuration you are trying (one is NDE63X image rooted and one is NDE63X image stock/unrooted). Here were my steps:
-> dePixel8 to unlock bootloader (because verizon edition pixel)
-> download NDE63X image from google and modified flash_all.sh to flash stock images to both slots manually
using the --slot _a/_b and --skip-secondary flags. Modified scripts below. At this point I confirmed that I could boot to both slots. I also verified bootloader lock/unlock again to make sure it was stock image on both slots
-> TWRP alpha2 to get recovery on both slots
-> with slot _b selected as active in TWRP, i installed the SuperSU v2.78 SR4 zip
-> with slot _a as active in TWRP, installed ElementalX-P-1.00 zip for the kernel patch to pass SafetyNet
voila, I now have non-rooted on slot _a and rooted on slot _b
Note that TWRP is not really a requirement for doing this. I had the same dual boot configuration working with SuperSU v2.78 SR3 rooting one slot directly. The only reason I needed TWRP is so that I can switch slots easily on the device and don't need a cable and a laptop just to switch the bootloader flag
Although, I got this to work it still falls short of what I really wanted to do. For my use-case I would really want an isolated userdata for the two slots so I can use the rooted slot as a complete sandbox. and then perhaps have a shared folder mechanism between the two. ...so if somebody has an idea on this, I'm all ears.
[UPDATE]: Note that the unrooted slot is still limited in the sense that safetynet checks fail and so AndroidPay etc.. that use that API will still not work. This, however, has little to do with the dual boot setup and more because SafetyNet now fails on just unlocked bootloader and we do need it unlocked. On Conchors' suggestion, I installed ElementalX kernel on slotA from TWRP and now my 'otherwise-stock' non-rooted image on slotA passes SafetyNet while slotB is successfully rooted
flash_all_slot-a.sh
Code:
fastboot flash --slot _a bootloader bootloader-sailfish-8996-012001-1608281716.img
fastboot reboot-bootloader
sleep 5
fastboot flash --slot _a radio radio-sailfish-8996-012511-1609191801.img
fastboot reboot-bootloader
sleep 5
#fastboot -w update image-sailfish-nde63x.zip
fastboot update --slot _a --skip-secondary image-sailfish-nde63x.zip
flash_all_slot-b.sh
Code:
fastboot flash --slot _b bootloader bootloader-sailfish-8996-012001-1608281716.img
fastboot reboot-bootloader
sleep 5
fastboot flash --slot _b radio radio-sailfish-8996-012511-1609191801.img
fastboot reboot-bootloader
sleep 5
#fastboot -w update image-sailfish-nde63x.zip
fastboot update --slot _b --skip-secondary image-sailfish-nde63x.zip
Click to expand...
Click to collapse
I switched it up a bit, and to be perfectly honest, the script is easier, this is just an alternate way of doing it
I did this for both slot_a and slot_b (not sure if it is needed for the flrst one, but that is what i did), both ways are correct, this way is much longer, but it gives some control, plus it's a nice learning process as it is pretty easy going.
If you are going to erase, erase first before you start anything, because you know...science.
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot erase vendor
the cache partition, i dont remember if this worked or not, I'm too tired to verify
Code:
fastboot flash --slot _b --skip-secondary bootloader "name-of-bootloader.img"
fastboot reboot-bootloader
fastboot flash --slot _b --skip-secondary radio "name-of-radio.img"
fastboot reboot-bootloader
fastboot flash --slot _b --skip-secondary system system.img
fastboot flash --slot _b --skip-secondary boot boot.img
fastboot flash --slot _b --skip-secondary vendor vendor.img
If you want to wipe everything, use the following commands next:
Code:
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
system.img and userdata.img take time to flash— the command prompt appears to stop. Let it do it's thing, when it's done the cursor will begin blinking again.
All dual-booting credit goes to hucqym; again, not my idea.
Slightly Off Topic -
Has anyone tried this on a specific slot, does it make any difference?) I haven't actually even thought of this till now
something like:
Code:
fastboot erase --slot _(a/b) --skip-secondary userdata
fastboot flash --slot _(a/b) --skip-secondary userdata userdata.img[/B]
theycallmerayj said:
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
Click to expand...
Click to collapse
ls2power said:
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
Click to expand...
Click to collapse
I was noticing quite a bit of space missing as well. what i did was boot into the slot I wanted as secondary (do this in TWRP), and i wiped just the system (which includes cache) and reflashed the system.img directly pulled from factory.zip. I noticed twice as much space had been gained then what was actually said to be there. I was a little surprised...it was over 5 gb I had gained while the system only said 2.5ish gb. (perhaps there was a second other_system.img wrapped up in it, I don't know. Then i went back to the primary slot and booted back up.
It's possible I got off course, I'm tired.
II am attempting to get back to full stock on my Pixel XL and I am okay with wiping it. I am coming from Rooted, TWRP, custom Kernel, and WETA Rom. I was having some issues with it acting up, and I want now to return to the full factory image. In order to do so, I attempted to run the flash-all.bat script from the Google page, and it seems as if all is going well, then, when it tries to flash the system.img, it fails and throws an error which says "FAILED (Remote: Partition [bootb] does not exist)" I have also tried flashing the factory image in pieces and get the same issue, and also when I try to do it through TWRP. I just want to go back to the way the phone came so I can start fresh. Any input on how to do so would be greatly appreciated. Note: the same error goes when I try to flash-all on slot a.
What version of adb are you running?
Make sure you have 1.0.36. Ref post http://forum.xda-developers.com/showthread.php?t=2932160
Try manually flashing to partition _a or _b. Such as fastboot flash system_a system.img.
I ran into the same issue and was able to flash everything to slot a manually by adding _a to the commands
harmohn said:
What version of adb are you running?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
The latest minimal adb fastboot
gettingerr said:
The latest minimal adb fastboot
Click to expand...
Click to collapse
Okay, just to be sure can you type "adb version" and then "fastboot --version" (without quotes) in a command line console. What were the outputs?
Android Debug Bridge version 1.0.35
Revision fc2a139a55f5-android
fastboot version fc2a139a55f5-android
Zavon said:
Try manually flashing to partition _a or _b. Such as fastboot flash system_a system.img.
I ran into the same issue and was able to flash everything to slot a manually by adding _a to the commands
Click to expand...
Click to collapse
I think that worked! Do I need to flash anything besides boot, system, and vendor? There are a lot of .img files in this folder from google. Do I do them all or just these three? Also, do I need to flash the radio?
Odd that Google wouldn't update their flash-all script to deal with the two slot setup..
gettingerr said:
Android Debug Bridge version 1.0.35
Revision fc2a139a55f5-android
fastboot version fc2a139a55f5-android
Click to expand...
Click to collapse
Right, you need to be on 1.0.36 for fastboot to "see" the partitions correctly. Refer to my initial comment for a download link.
gettingerr said:
I think that worked! Do I need to flash anything besides boot, system, and vendor? There are a lot of .img files in this folder from google. Do I do them all or just these three? Also, do I need to flash the radio?
Odd that Google wouldn't update their flash-all script to deal with the two slot setup..
Click to expand...
Click to collapse
I didn't flash any of the other stuff. Only boot, system, and vendor.
Not sure what causes the mismatch in names of the partitions.
Download the free Unified Toolkit. It works across a large number of Android devices. It takes the hassle out of a lot of ****, including this. It will flash the entire factory package by itself. I had to do this to fix my phone from a recovery bootloop after flash-all.bat failed me too.
Hi guys,
I installed the latest Android P factory image (without -w) and now the phone always boots into recovery right after booting into the system. I see the system for one second and then the phone boots into recovery mode. Does anybody have an idea how to fix this?
I already tried this command
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/1da4000.ufshc/by-name/misc
It was successful:
Code:
dd: writing '/dev/block/platform/soc/1da4000.ufshc/by-name/misc': No space left on device
2049+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.049919 seconds, 20.0MB/s
It did not fix the issue though. I also tried this command:
Code:
fastboot oem fb_mode_clear
-> This command was unknown
I cannot find find anything else that might help.
Does anybody have an idea how I can get rid of the recovery bootloop?
I have not tried a factory reset with the wipe enabled since I want this to be my last option.
Thank you!
JDUS said:
Hi guys,
I installed the latest Android P factory image (without -w) and now the phone always boots into recovery right after booting into the system. I see the system for one second and then the phone boots into recovery mode. Does anybody have an idea how to fix this?
I already tried this command
It was successful:
It did not fix the issue though. I also tried this command: -> This command was unknown
I cannot find find anything else that might help.
Does anybody have an idea how I can get rid of the recovery bootloop?
I have not tried a factory reset with the wipe enabled since I want this to be my last option.
Thank you!
Click to expand...
Click to collapse
Did you fastboot the image to both slots? Your active slot could be corrupted. I'm also assuming you have the latest platform-tools. You might also try different USB A to USB C cables and ports. You may have to clean fastboot and wipe your device as well.
Badger50 said:
Did you fastboot the image to both slots? Your active slot could be corrupted. I'm also assuming you have the latest platform-tools. You might also try different USB A to USB C cables and ports. You may have to clean fastboot and wipe your device as well.
Click to expand...
Click to collapse
I downloaded the latest Android P factory image and extracted it. Then I removed -w so it would not wipe my data and I simply executed flash-all.bat.
I am not sure if this installs it to both slots. Does it?
I have a partial working Android Q now...I was able to install Android Q again using the same method but at least it boots into the OS now. A lot of things don't work now. My home button and mobile data for example...
I will try to install factory P once again and maybe this time I won't be stuck in a recovery loop.
JDUS said:
I downloaded the latest Android P factory image and extracted it. Then I removed -w so it would not wipe my data and I simply executed flash-all.bat.
I am not sure if this installs it to both slots. Does it?
I have a partial working Android Q now...I was able to install Android Q again using the same method but at least it boots into the OS now. A lot of things don't work now. My home button and mobile data for example...
I will try to install factory P once again and maybe this time I won't be stuck in a recovery loop.
Click to expand...
Click to collapse
It does not install to both slots. Since your on Q and you have a working OS, I would backup your data since you may have to clean fastboot back to Pie. Or at least fastboot Pie to both slots.
Badger50 said:
It does not install to both slots. Since your on Q and you have a working OS, I would backup your data since you may have to clean fastboot back to Pie. Or at least fastboot Pie to both slots.
Click to expand...
Click to collapse
Thank you for your help but I want to make sure I understand you correctly. How would I fastboot Pie to both slots? Using fastboot --slot all?
JDUS said:
Thank you for your help but I want to make sure I understand you correctly. How would I fastboot Pie to both slots? Using fastboot --slot all?
Click to expand...
Click to collapse
After I flash it to one slot, I then use..fastboot --set active=a or b.... depending of course on what you need to switch it to :good:
Badger50 said:
After I flash it to one slot, I then use..fastboot --set active=a or b.... depending of course on what you need to switch it to :good:
Click to expand...
Click to collapse
That makes sense. Do you flash bootloader, radio and the system image to both slots? Or just the system?
JDUS said:
That makes sense. Do you flash bootloader, radio and the system image to both slots? Or just the system?
Click to expand...
Click to collapse
I fastboot the whole factory image to both slots with the -w removed to persevere data as you did :good:
Badger50 said:
I fastboot the whole factory image to both slots with the -w removed to persevere data as you did :good:
Click to expand...
Click to collapse
Looks like I am on slot b right now. Does it matter which slot I use to boot after I flashed the image? Also you were right with your thought. My slot a is corrupt according to
Code:
fastboot getvar all
Code:
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
Edit:
Okay so I ran the flash-all.bat on b slot , then I switched to the a slot and ran the flash-all.bat file again. Now I have the opposite effect.
current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
It boots into recovery mode as soon as I boot into the system.
JDUS said:
Looks like I am on slot b right now. Does it matter which slot I use to boot after I flashed the image? Also you were right with your thought. My slot a is corrupt according to
Click to expand...
Click to collapse
Doesn't matter at all since you need to flash it to both slots anyways. Go with B for starters, then switch it to A when done :good:
Badger50 said:
Doesn't matter at all since you need to flash it to both slots anyways. Go with B for starters, then switch it to A when done :good:
Click to expand...
Click to collapse
I did exactly that. I edited my comment before. Now I am stuck with the opposite effect. Now a is bootable but b is not. Let me try to flash it to both at the same time with fastboot --slot all somehow...
JDUS said:
I did exactly that. I edited my comment before. Now I am stuck with the opposite effect. Now a is bootable but b is not. Let me try to flash it to both at the same time with fastboot --slot all somehow...
Click to expand...
Click to collapse
Hmmmm...maybe, fastboot flash-all --slot all...might work. If not, then clean flashing and wiping might be in order. Unfortunately!
Badger50 said:
Hmmmm...maybe, fastboot flash-all --slot all...might work. If not, then clean flashing and wiping might be in order. Unfortunately!
Click to expand...
Click to collapse
You mean running the flash-all.bat file on both slots but this time with the wipe enabled? Looks like it is my only option. I cannot get it to work. I tried using slot all but that did not work either.
JDUS said:
You mean running the flash-all.bat file on both slots but this time with the wipe enabled? Looks like it is my only option. I cannot get it to work. I tried using slot all but that did not work either.
Click to expand...
Click to collapse
I didn't know if it would work with -w removed or not. However, when you leave the -w in, it will flash to both slots, but that will wipe your device. You may try fastbooting the boot, system and vendor images to both slots to see if you can boot to the OS. If not, then you'll likely have to clean fastboot the factory image and wipe the device. It sucks I know, but sometimes there's no other options.
Alright so the factory reset with wipe enabled worked. Now I am setting up everything again I did not know that you can restore your old update from the cloud...it is restoring all my apps right now. That would be amazing. I did not have any important data on my phone and the photos were saved in the cloud but I did not want to reinstall all my apps again. Looks like it is doing this right now. That is great. Thank you a lot!
Some day we might get real internet out here in the boonies and that new fangled cloud stuff might be useful... Lol
You cant downgrade from the Q beta to P without wiping data partition. Happened to me too, wiping data fixed it. So just boot to twrp, wipe data partition, flash the P image again and it should be fixed.
Mikulec said:
You cant downgrade from the Q beta to P without wiping data partition. Happened to me too, wiping data fixed it. So just boot to twrp, wipe data partition, flash the P image again and it should be fixed.
Click to expand...
Click to collapse
I thought there might be a way to do it anyway. Do you know why you have to wipe the data partition?
Also I am so glad to have root back and AdAway...could not deal with all these ads everywhere for even one day.
JDUS said:
I thought there might be a way to do it anyway. Do you know why you have to wipe the data partition?
Also I am so glad to have root back and AdAway...could not deal with all these ads everywhere for even one day.
Click to expand...
Click to collapse
Well to be honest Google says that if you want to downgrade from beta you have to do factory reset. But I have no idea why is that necessary.
Mikulec said:
Well to be honest Google says that if you want to downgrade from beta you have to do factory reset. But I have no idea why is that necessary.
Click to expand...
Click to collapse
I read that too yeah.. I was just curious about the technical background why this is necessary. Maybe someone has an idea? To me wiping everything felt like giving up yesterday. It is like formatting your PC if you have a problem. Instead I want to know what causes it so I can fix it
Surprised that I haven't come across too much regarding this tablet. It's relatively cheap, but has a wonderful screen, with cel data and SD card support. And not a bad resolution. (Not 4K, but ALMOST 2k...) This device seems to be running a SpreadTrun / SPD system under the hood.
Having issues getting it rooted and bootloader unlocked.
First, Rooting via boot.img and Magisk -
I am able to get the boot.img file and have Magisk patch it fine. However, when I go to re-write the boot.img file, fastboot gives me the following:
C:\>fastboot flash boot_a magisk_patched-22100_2U5Ga.img
Warning: skip copying boot_a image avb footer (boot_a partition size: 0, boot_a image size: 67108864).
Sending 'boot_a' (65536 KB) OKAY [ 2.422s]
Writing 'boot_a' FAILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')
fastboot: error: Command failed
SPD's UpgradeFlash won't let me select JUST to flash the boot file - it forces everything to be flashed, which resets the device. Because of that, when I insert the patched boot.img in, it causes the tablet to bootloop.
Trying to unlock bootloader -
Reading through different methods for SPD devices, I'm running into deadends. With both ADB Debug and OEM Unlock enabled, running the following commands don't work:
C:\>fastboot flashing unlock
FAILED (remote: 'unknown cmd.')
C:\>fastboot oem unlock
FAILED (remote: 'Unlock bootloader fail.')
I thought that perhaps the method of flashing the signature (signature.pim file) was needed. However, following that attempt, the command yields:
C:\>fastboot flashing unlock signature.bin
fastboot: usage: unknown 'flashing' command unlock
(Same error is given for 'unlock_critical' and 'unlock_bootloader'.)
Anyone know of an alternate way to flash JUST the boot.img files to an SPD device?
Quick bump!
One interesting thing I have noticed - every time after I run the second command ('oen unlock'), any command sent AFTER that will hang. As if the tablet's expecting something else.
Any luck? I've also got this tablet, seems like unisoc have different bootloader unlock procedure, read that it needs linux with custom adb tools
I actually unlocked the bootloader on mine several months ago. Details aren't fresh in my mind but I do remember a few things that may help you.
1) You absolutely need the signature file. I got mine by installing an app "spreatrum tools" on the tablet.
2) It only works with a specific version of fastboot.
3) According to my terminal history, the command to unlock could be "fastboot.exe flashing unlock_bootloader signature.bin" or the one posted by OP: "fastboot flashing unlock signature.bin". At least one of these works but I don't remember which since I used them both.
Pretty sure I got both the working version of fastboot (windows version, not linux) and the app here on the forum. Whoever posted those files originally deserves the credits but, again, I don't remember who or where so... Luckily I still have both files on my NAS so I'm attaching them.
Anyway, there, have fun.
So this can also work, nice!
troolie said:
I actually unlocked the bootloader on mine several months ago. Details aren't fresh in my mind but I do remember a few things that may help you.
Anyway, there, have fun.
Click to expand...
Click to collapse
Thanks so much, already unlocked my BL (through modified adb via Linux) but can't proceed to root it, have you rooted yours?
Nope. My plan was to unlock in order to install a custom recovery as I thought there's a good chance the one for iplay40 might work. Turns out I ended up with a brick so I went back to stock.
My immediate concern was to get rid of system apps but adb shell works well enough for that so...
Actually, I'm more interested in running generic GSI if at all possible, considering alldocube is unlikely to ever update the stock rom.
troolie said:
I actually unlocked the bootloader on mine several months ago. Details aren't fresh in my mind but I do remember a few things that may help you.
Click to expand...
Click to collapse
Vvtaewoo12 said:
Any luck? I've also got this tablet, seems like unisoc have different bootloader unlock procedure, read that it needs linux with custom adb tools
Click to expand...
Click to collapse
Sorry for the silence guys, had a death in the family that took me away from playing with this tablet for a while.
Glad you both got it - I actually was able to get in touch with someone AT AlldoCube, and they replied saying that the bootloader IS UNLOCKED in the same fashion that the iPlay40 is. (Which isn't too much of a surprise - the back cover of my kPad actually has the iPlay 40 model number on it. Heh.) I followed the instructions in the iPlay 40 thread exactly (including the one command that's run that the output seems to not be used), and it worked.
Like you both, though, I haven't been able to root - Because of the family issues, I haven't tried in a while, but I remember getting as far as trying to flash a modified Magisk boot.img - at which point, the tablet goes into bootloop. I blieve that we need a signed vbmeta file, though I have no idea yet how to generate/flash that.
I have NOT tried the iPlay40 rooting instructions in one post, and I'm admittedly not even sure that I'm using the Spedtrum flashing applications correctly.
Help me unlock bootloader ipay 40
U have trailer video URL/??
U use Ubuntu linux but do not!!
Taoismixi said:
U use Ubuntu linux but do not!!
Click to expand...
Click to collapse
Wrong thread. This is not about the iPlay 40.
Hello,
I am sorry to bother you with this stupidity but i soft bricked (stuck in fastboot) my Realme GT Master Edition (RMX3363GDPR).
The phone is unlocked but i am unfamilear with flashing this phone and it's partition system.
Anyone can help me? I tried flashing with RealmeOppo flash tool but it or hangs or tells me it's succeeded but it's clearly not. It stays on fastboot mode.
Thanks in advance
pieterrees said:
Hello,
I am sorry to bother you with this stupidity but i soft bricked (stuck in fastboot) my Realme GT Master Edition (RMX3363GDPR).
The phone is unlocked but i am unfamilear with flashing this phone and it's partition system.
Anyone can help me? I tried flashing with RealmeOppo flash tool but it or hangs or tells me it's succeeded but it's clearly not. It stays on fastboot mode.
Thanks in advance
Click to expand...
Click to collapse
https://sourceforge.net/projects/nippongsi/files/Pixel%20-%20Pixel5-Tiramisu-Beta2.1%20-%20KAVHT4FFWN/Pixel5-Tiramisu-Beta2.1-AB-Tiramisu-20220527-NipponGSI.img.gz/download
extract the .gz to become a .img, with 7zip or whatever,then rename it to system.img, put to c drive not under any folder, then execute fastboot command:
fastboot flash system C:\system.img
if fail then replace with
fastboot flash system_a C:\system.img
and
fastboot flash system_b C:\system.img
then
fastboot -w
fastboot reboot
if you are really lucky it will boot up into system
do at your own risk
Thank for your reply. How is Pixel5 firmware compatible with Realme GT Master Edition?
NVM, fixed it already.
pieterrees said:
Thank for your reply. How is Pixel5 firmware compatible with Realme GT Master Edition?
Click to expand...
Click to collapse
ported (added compatibility) for generic android 9 or higher devices
pieterrees said:
NVM, fixed it already.
Click to expand...
Click to collapse
glad you fixed it
LR7875 said:
https://sourceforge.net/projects/nippongsi/files/Pixel%20-%20Pixel5-Tiramisu-Beta2.1%20-%20KAVHT4FFWN/Pixel5-Tiramisu-Beta2.1-AB-Tiramisu-20220527-NipponGSI.img.gz/download
extract the .gz to become a .img, with 7zip or whatever,then rename it to system.img, put to c drive not under any folder, then execute fastboot command:
fastboot flash system C:\system.img
if fail then replace with
fastboot flash system_a C:\system.img
and
fastboot flash system_b C:\system.img
then
fastboot -w
fastboot reboot
if you are really lucky it will boot up into system
do at your own risk
Click to expand...
Click to collapse
I did all that on the phone but the phone is on fastboot ????????? What is the solution please?
nighetspy said:
I did all that on the phone but the phone is on fastboot ????????? What is the solution please?
Click to expand...
Click to collapse
Fastboot does not properly recognize your device?
Try fastboot reboot fastboot before executing the commands
LR7875 said:
Fastboot does not properly recognize your device?
Try fastboot reboot fastboot before executing the commands
Click to expand...
Click to collapse
(remote: 'Partition not found') fastboot error please help me
nighetspy said:
(remote: 'Partition not found') fastboot error please help me
Click to expand...
Click to collapse
Tried system, system_a and system_b?
LR7875 said:
Tried system, system_a and system_b?
Click to expand...
Click to collapse
yes The problem is still there
nighetspy said:
yes The problem is still there
Click to expand...
Click to collapse
GSI on Super Partitions
I want so much to install GSI, but when I was going to flash I saw that my device "doesn't have System" Partition. It's called Super Partition there. Does anyone knows how can I install it? I tried some video tutorials, but it always get an Error...
forum.xda-developers.com
LR7875 said:
GSI on Super Partitions
I want so much to install GSI, but when I was going to flash I saw that my device "doesn't have System" Partition. It's called Super Partition there. Does anyone knows how can I install it? I tried some video tutorials, but it always get an Error...
forum.xda-developers.com
Click to expand...
Click to collapse
fastboot flash <PARTITION> <FILENAME>. ......... Nothing new
pieterrees said:
NVM, fixed it already.
Click to expand...
Click to collapse
Could you please tell me how you fixed it, dealing with the same issue
battus said:
Could you please tell me how you fixed it, dealing with the same issue
Click to expand...
Click to collapse
I also want to know how this problem was solved
Allright,
I had a GDPR version of the firmware. I soft bricked my phone by accident. Then I flashed
Code:
RMX3363export_11_A.04_2021080317040000.ofp
and then it was an export version.
I found other ofp's but they didn't work (alltough for me..)
After i successfully flashed my phone i had update issues so i flashed
Code:
RMX3363export_11_A.09_2021122118530211.ofp
This works and a couple of hours later i even get the Realme UI 3.0 update. (this was my goal before i bricked my phone )
I used this tool:
Code:
OppoRealme-OFP-Flash
Beware, if you flashed your phone and it does not work, try changing your Slot in Fastboot.
If you don't have the correct slot (or the new software is flashed onanother slot, it will keep rebooting to fastboot)
I hope my explanation helps. I was desperate and spent three days fixing my phone. When i succeeded i tried to flash the same file from my laptop. This didn't work.I don't know why.
Good luck
pieterrees said:
Allright,
I had a GDPR version of the firmware. I soft bricked my phone by accident. Then I flashed
Code:
RMX3363export_11_A.04_2021080317040000.ofp
and then it was an export version.
I found other ofp's but they didn't work (alltough for me..)
After i successfully flashed my phone i had update issues so i flashed
Code:
RMX3363export_11_A.09_2021122118530211.ofp
This works and a couple of hours later i even get the Realme UI 3.0 update. (this was my goal before i bricked my phone )
I used this tool:
Code:
OppoRealme-OFP-Flash
Beware, if you flashed your phone and it does not work, try changing your Slot in Fastboot.
If you don't have the correct slot (or the new software is flashed onanother slot, it will keep rebooting to fastboot)
I hope my explanation helps. I was desperate and spent three days fixing my phone. When i succeeded i tried to flash the same file from my laptop. This didn't work.I don't know why.
Good luck
Click to expand...
Click to collapse
How long does it take to flash after this? fastboot --set-active=a ؟؟؟؟؟؟؟؟؟؟؟
I just flashed the ofp, after that i tried to reboot.
Then it didn't work and the device booted back into fastboot. After that I did
Code:
fastboot --set-active=other
and after that
Code:
fastboot reboot
and then it worked.
Maybe a vague tip: when you flashed it correctly and you are on the wrong slot it takes longer to boot into fastboot then when your device is bricked. Then you can change slots and (for me) that did the trick.
Good luck
How long does it take for this to end?
fastboot --set-active=other ؟؟
؟؟
a couple of seconds. When it takes forever try rebooting fastboot and try changing slots again or flash again (on another computer).
pieterrees said:
a couple of seconds. When it takes forever try rebooting fastboot and try changing slots again or flash again (on another computer).
Click to expand...
Click to collapse
What region is your phone used ؟
It works fine with you? RMX3363_11_A.09_2021122118530211.ofp ؟؟