Related
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
Why can't you download an earlier firmware?
schmeggy929 said:
Why can't you download an earlier firmware?
Click to expand...
Click to collapse
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
schmeggy929 said:
i downloaded the asus firmware for 10.14.1.47. extract zip and you get a user.zip. extracted the boot.img. I fastboot erase boot, system, format system, data and cache(as you did)
fastboot -i 0x0B05 flash boot boot.img then
fastboot -i 0x0B05 flash system blob then
fastboot -i 0x0B05 flash system UL-K00C-US-10.14.1.47-user.zip
rebooted back into fastboot and bootloader showed 10.14.1.47 version.
Click to expand...
Click to collapse
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Ikkerens said:
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Click to expand...
Click to collapse
you are going to get that along with a few more errors. Wait until it is done. It will take like 10 mins and finish.
when it is done reboot in bootloader and you should see the version change.
schmeggy929 said:
you are going to get that along with a few more errors. Wait until it is done. I will take like 10 mins and finish.
Click to expand...
Click to collapse
You're getting this wrong, it does not do anything. The process immediately quits.
Ikkerens said:
You're getting this wrong, it does not do anything. The process immediately quits.
Click to expand...
Click to collapse
Ok when you get that message do you get a blinking curser?
Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
lpdunwell said:
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
Click to expand...
Click to collapse
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Ikkerens said:
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Click to expand...
Click to collapse
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
lpdunwell said:
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
Click to expand...
Click to collapse
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Ikkerens said:
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Click to expand...
Click to collapse
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
lpdunwell said:
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
Click to expand...
Click to collapse
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Ikkerens said:
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Click to expand...
Click to collapse
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Snah001 said:
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Click to expand...
Click to collapse
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Ikkerens said:
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Click to expand...
Click to collapse
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
pelago said:
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Click to expand...
Click to collapse
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Snah001 said:
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
Click to expand...
Click to collapse
Already too late, it has been RMA'd, and then, I had nothing to flash it with.
Ikkerens said:
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Click to expand...
Click to collapse
Well I meant, what should a root user do to try and protect themselves against bricking their device like you did? Is it a matter of making sure that CWM or TWRP is on the device as a recovery partition? And are those available on TF701T yet?
Oh dear. That's a lot gone wrong.
Cwm is available and that works.
It's made by drgravy. I use it in my unbrick tut.
All i can say is, root --> cwm --> backup.
Sent from my GT-I9505 using xda app-developers app
That CWM wouldn't boot for me :/
So here is my problem , after trying to install a custom rom on my razr i i may have broken something in the system and now he isnot booting anymore , i'm stuck in the fastboot mode but not any of the options is working and it keeps telling me that my pds partition is broken ...
I'm a complete newbie and i have no idea how to fix it so please help me !
doud1998 said:
So here is my problem , after trying to install a custom rom on my razr i i may have broken something in the system and now he isnot booting anymore , i'm stuck in the fastboot mode but not any of the options is working and it keeps telling me that my pds partition is broken ...
I'm a complete newbie and i have no idea how to fix it so please help me !
Click to expand...
Click to collapse
What if u flash with fastboot the pds partition? And what is exactly the error u get?
If that doesn't work just flash with rsd-lite (latest) and your firmware (latest) and recover it. From then on u can try again.
Hazou said:
What if u flash with fastboot the pds partition? And what is exactly the error u get?
If that doesn't work just flash with rsd-lite (latest) and your firmware (latest) and recover it. From then on u can try again.
Click to expand...
Click to collapse
thanks for responding fast . I'll try that but how can i flash the pds partition and where can i find this partition? As well where can i find the firmware for my phone?
thanks very much for helping me
doud1998 said:
thanks for responding fast . I'll try that but how can i flash the pds partition and where can i find this partition? As well where can i find the firmware for my phone?
thanks very much for helping me
Click to expand...
Click to collapse
See my signature
I assume you have a working adb and fastboot, otherwise u couldn't have installed the recovery.
Your firmware can be found under section E.
When you have downloaded your fimware (always 4.1.2). Extract it and flash the pds_signed or pds.bin. Something with pds.
This can be done by moving the pds* to the directory with the fastboot executable. Then boot into ap fastboot mode and check if your device is recognized by using "fastboot devices". If yes, do the following command to flash the pds partition "fastboot flash pds (pds-file)"
If it doesn't work, post the results. Not only that is says an error, but post the error string.
Hazou said:
See my signature
I assume you have a working adb and fastboot, otherwise u couldn't have installed the recovery.
Your firmware can be found under section E.
When you have downloaded your fimware (always 4.1.2). Extract it and flash the pds_signed or pds.bin. Something with pds.
This can be done by moving the pds* to the directory with the fastboot executable. Then boot into ap fastboot mode and check if your device is recognized by using "fastboot devices". If yes, do the following command to flash the pds partition "fastboot flash pds (pds-file)"
If it doesn't work, post the results. Not only that is says an error, but post the error string.
Click to expand...
Click to collapse
I'm really sorry to annoy you for that but i don't get what you mean by "section E"
doud1998 said:
I'm really sorry to annoy you for that but i don't get what you mean by "section E"
Click to expand...
Click to collapse
I meant, in my signature under my post u can find within the link INDEX/GUIDE, ALL Things RAZR I under paragraph/ section E a link to all the firmwares available for the Razr I.
But in this case i will post the full link to the firmware site, here.
I've download the zip but there is no pds file and i don't know how to use rsd (or is it anormal that the phone reference appear nowhere?!)
i tried to flash recovery_signed but i have the error
Checking fs on partition pds...
E:can't repaire partition pds
E:failed to mount PDS partition
doud1998 said:
I've download the zip but there is no pds file and i don't know how to use rsd (or is it anormal that the phone reference appear nowhere?!)
Click to expand...
Click to collapse
I looked a bit further into your problem, u may have this problem: this
So what we now are going to do is the following.
First can u enter recovery? and if i can, do u have a nandroid backup. If yes, restore it and just boot up the phone.
If u don't have the above. (all can be found with a bit of searching in the link in my signature)
1. Install RSD-Lite 6.1.x
2. Install the USB drivers for the phone
3. U already downloaded the right firmware (latest and the one from your region)
4. Boot in AP Fastboot and connect phone to USB port PC
5. In RSD-Lite u won't see your device. It doesn't have a system installed.
6. In RSD-Lite search in the above bar for the firmware zip file.
7. Click on flash or something. (there is a RSD-Lite tutorial in my signature in my post)
8. See what happens
9. Report back
Hazou said:
I looked a bit further into your problem, u may have this problem: this
So what we now are going to do is the following.
First can u enter recovery? and if i can, do u have a nandroid backup. If yes, restore it and just boot up the phone.
If u don't have the above. (all can be found with a bit of searching in the link in my signature)
1. Install RSD-Lite 6.1.x
2. Install the USB drivers for the phone
3. U already downloaded the right firmware (latest and the one from your region)
4. Boot in AP Fastboot and connect phone to USB port PC
5. In RSD-Lite u won't see your device. It doesn't have a system installed.
6. In RSD-Lite search in the above bar for the firmware zip file.
7. Click on flash or something. (there is a RSD-Lite tutorial in my signature in my post)
8. See what happens
9. Report back
Click to expand...
Click to collapse
when i run rsd i can select the firmware xml but the commands 'start', 'show devices', or 'decompress and flash' are disabled (nothing happen)
+> i don't have any backup and i can't go to recovery , when it turns on it automaticly stuck to the ap fastboot menu
doud1998 said:
when i run rsd i can select the firmware xml but the commands 'start', 'show devices', or 'decompress and flash' are disabled (nothing happen)
Click to expand...
Click to collapse
Are you sure you installed drivers? RSD Lite should show Fastboot smi S as connected.
If you have installed drivers, and nothing is being detected, then you might want to prepare for several hours of headaches and lots of swearing.
You might have a chance doing this:
You will need to flash a custom recovery. If you can get CWM or TWRP working, you might have a chance to flash a zip.
i.e.
Code:
fastboot flash recovery recovery.img
Since your PDS is damaged, Omar's MotoJB ROM will probably not work, so you will need to flash a clean, stock ROM.
The only stock ROMs I've found (that can be flashed with custom recovery) are:
deodexed Retail Great Britain ICS ROM
odexed Retail Great Britain ICS ROM
Note that going back to ICS using this zip file will not brick your device (at least it didn't for my phone) unless you do it with RSD Lite.
But please don't hold me responsible if it makes things worse for you.
If you manage to flash this and it works, you can then try the PDS fix.
Good luck... :good:
waj3k said:
Are you sure you installed drivers? RSD Lite should show Fastboot smi S as connected.
If you have installed drivers, and nothing is being detected, then you might want to prepare for several hours of headaches and lots of swearing.
You might have a chance doing this:
You will need to flash a custom recovery. If you can get CWM or TWRP working, you might have a chance to flash a zip.
i.e.
Code:
fastboot flash recovery recovery.img
Since your PDS is damaged, Omar's MotoJB ROM will probably not work, so you will need to flash a clean, stock ROM.
The only stock ROMs I've found (that can be flashed with custom recovery) are:
deodexed Retail Great Britain ICS ROM
odexed Retail Great Britain ICS ROM
Note that going back to ICS using this zip file will not brick your device (at least it didn't for my phone) unless you do it with RSD Lite.
But please don't hold me responsible if it makes things worse for you.
If you manage to flash this and it works, you can then try the PDS fix.
Good luck... :good:
Click to expand...
Click to collapse
thanks for your responce but the threads for these roms have deadlink so i can't download the files....Any idea where i could find them?
doud1998 said:
thanks for your responce but the threads for these roms have deadlink so i can't download the files....Any idea where i could find them?
Click to expand...
Click to collapse
I know, I just uploaded Deodexed Retail Great Britain ICS:
Here you go. There should be a download icon at the top.
give me the right access (i'm [email protected])
Sorry, forgot to set it to public, should be fixed now.
so now i have to flash the boot.img or what? i'm not really sure what to do with this zip
You need to flash custom recovery and then you can install a zip.
Here is a tutorial on how to use recovery, if you're unsure.
i can't make works neither cwm nor twrp
doud1998 said:
So here is my problem, after trying to install a custom rom on my razr i, i may have broken something in the system
Click to expand...
Click to collapse
may i ask you what u have exactly done to install your "custom rom"?
1. Bootloader unlocked?
2. Custom Recovery installed?
3. How did you installed your rom?
4. Which custom rom?
Hi. I'm on Marshmallow and whenever I try to install recovery via fastboot, I go down to recovery and boot it, but it always goes to the battery charging logo and reboots.
Any ideas on how to solve this?
Thanks!
Sesamechicken said:
Hi. I'm on Marshmallow and whenever I try to install recovery via fastboot, I go down to recovery and boot it, but it always goes to the battery charging logo and reboots.
Any ideas on how to solve this?
Thanks!
Click to expand...
Click to collapse
Is your bootloader unlocked?
Are you flashing recovery like this:
fastboot flash recovery twrp-3.0.2-1-victara.img
Then booting into recovery right away?
Yes my bootloader is unlocked and yes that's exactly how I flash it (except I named it recovery)
And yes, I boot into recovery right away via the bootloader options.
Gus Ghanem said:
Is your bootloader unlocked?
Are you flashing recovery like this:
fastboot flash recovery twrp-3.0.2-1-victara.img
Then booting into recovery right away?
Click to expand...
Click to collapse
Forgot to quote sorry
Sesamechicken said:
Yes my bootloader is unlocked and yes that's exactly how I flash it (except I named it recovery)
And yes, I boot into recovery right away via the bootloader options.
Click to expand...
Click to collapse
What is the phone booting into? Stock?
If you have the latest stock firmware files, try:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash recovery recovery.img
Only use TWRP or Cyanogen Recovery, they are the only ones supported.
Gus Ghanem said:
What is the phone booting into? Stock?
If you have the latest stock firmware files, try:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash recovery recovery.img
Only use TWRP or Cyanogen Recovery, they are the only ones supported.
Click to expand...
Click to collapse
OK I will try that. Stock marshmallow right?
I was on complete stock and used windroid to unlock bootloader and I was aware of the problem whilst installing custom recovery.
Am I able to flash SuperSU via flash boot since that's mainly what I'm looking for?
Thanks
Sent from my XT1095 using XDA-Developers mobile app
Sesamechicken said:
OK I will try that. Stock marshmallow right?
I was on complete stock and used windroid to unlock bootloader and I was aware of the problem whilst installing custom recovery.
Am I able to flash SuperSU via flash boot since that's mainly what I'm looking for?
Thanks
Sent from my XT1095 using XDA-Developers mobile app
Click to expand...
Click to collapse
Make sure you never downgrade the bootloader or partition table, so yes, use the latest Android 6.0 MarshMallow firmware, in case something gets corrupted and you need to reflash the partition table and/or bootloader, or even the full stock firmware, so you can start again.
Flashing SuperSU is always risky, and I've never done it; I only use CM's built-in Root Access.
Gus Ghanem said:
Make sure you never downgrade the bootloader or partition table, so yes, use the latest Android 6.0 MarshMallow firmware, in case something gets corrupted and you need to reflash the partition table and/or bootloader, or even the full stock firmware, so you can start again.
Flashing SuperSU is always risky, and I've never done it; I only use CM's built-in Root Access.
Click to expand...
Click to collapse
Just tried that to no avail.
Is there anyway to root without having a custom recovery?
Sesamechicken said:
Just tried that to no avail.
Is there anyway to root without having a custom recovery?
Click to expand...
Click to collapse
I really don't know, as I only have the one phone, and don't want to take any risks with, I never looked into rooting, and never needed it anyway. But if I ever need the odd root access, CyanogenMod does it for me.
There are apps like King Root, which I've never used:
https://kingroot.net/
TRY AT YOUR OWN RISK.
Gus Ghanem said:
I really don't know, as I only have the one phone, and don't want to take any risks with, I never looked into rooting, and never needed it anyway. But if I ever need the odd root access, CyanogenMod does it for me.
There are apps like King Root, which I've never used:
https://kingroot.net/
TRY AT YOUR OWN RISK.
Click to expand...
Click to collapse
Ok, so I tried the Kingroot method and it took out my wifi and cellular network (doesn't turn on).
So I flashed the system files in the marshmallow and now my system doesn't boot. xD!
One question: is there any single marshmallow system zip file I could flash in one go to increase chances of resurrection? What's annoying is that I can't seem to get custom recovery working.
Thanks
Gus Ghanem said:
I really don't know, as I only have the one phone, and don't want to take any risks with, I never looked into rooting, and never needed it anyway. But if I ever need the odd root access, CyanogenMod does it for me.
There are apps like King Root, which I've never used:
https://kingroot.net/
TRY AT YOUR OWN RISK.
Click to expand...
Click to collapse
Nevermind! I am so f****ng stupid!!!!
I NEVER ACTUALLY SELECTED USING UP VOLUME I ALWAYS CLICKED THE POWER BUTTON WHICH REBOOTED. I AM ACTUALLY SO STUPID.
Thanks anyways!
Sesamechicken said:
Ok, so I tried the Kingroot method and it took out my wifi and cellular network (doesn't turn on).
So I flashed the system files in the marshmallow and now my system doesn't boot. xD!
One question: is there any single marshmallow system zip file I could flash in one go to increase chances of resurrection? What's annoying is that I can't seem to get custom recovery working.
Thanks
Click to expand...
Click to collapse
Since we don't know for sure what's causing it not to boot, might as well flash the whole fimware, I think you can paste all the commands at once, or create a batch file in the firmware folder, flash.bat, shift+right-click, open command window here... type flash.bat
Or you can use RSD Lite
If/when you lose signal/data/wifi you can try flashing just the modems from stock:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
I was curious, is there anyway to flash the firmware and modem through fastboot instead of TWRP? I accidentally downloaded the OP3 firmware instead of OP3T and then flashed it and well you know how that goes. Thankfully this phone almost impossible to brick even when doing the worst. It shows up in the computer and my bootloader is unlocked, and i was wondering, instead of losing everything and following the unbrick guide if there are actually commands or ways to flash it through fastboot so i don't have to fully wipe the phone? I have TWRP backups that are from yesterday on the phone, so if there was a way to restore that at the very least if i did have to do the full flash then thats fine too. I guess if the unbrick tool didn't wipe out internal storage or something thats fine. Any help is appreciated.
M3drvr said:
I was curious, is there anyway to flash the firmware and modem through fastboot instead of TWRP? I accidentally downloaded the OP3 firmware instead of OP3T and then flashed it and well you know how that goes. Thankfully this phone almost impossible to brick even when doing the worst. It shows up in the computer and my bootloader is unlocked, and i was wondering, instead of losing everything and following the unbrick guide if there are actually commands or ways to flash it through fastboot so i don't have to fully wipe the phone? I have TWRP backups that are from yesterday on the phone, so if there was a way to restore that at the very least if i did have to do the full flash then thats fine too. I guess if the unbrick tool didn't wipe out internal storage or something thats fine. Any help is appreciated.
Click to expand...
Click to collapse
If you're experienced, you can actually flash each individual partition image file back to each partition on your phone using fastboot flash file partition. So yes, if you know what you're doing you could just restore the firmware partitions and you should be back on track. However if you accidentally flash to the wrong partitions you could potentially brick your phone. ?
pitrus- said:
If you're experienced, you can actually flash each individual partition image file back to each partition on your phone using fastboot flash file partition. So yes, if you know what you're doing you could just restore the firmware partitions and you should be back on track. However if you accidentally flash to the wrong partitions you could potentially brick your phone.
Click to expand...
Click to collapse
I'm perfectly comfortable flashing partitions. Done it many times with old HTC's and Nexus's. I just need to know what the actual names of the files are that i'd need to extract from the zips is the other thing.
M3drvr said:
I'm perfectly comfortable flashing partitions. Done it many times with old HTC's and Nexus's. I just need to know what the actual names of the files are that i'd need to extract from the zips is the other thing.
Click to expand...
Click to collapse
Well, I've never really had to do this on the 3t. Last was on an old Huawei mediapad, but you can Google all the partition dumps in the latest full OTA zip, some are self explaining.
hey @M3drvr,
i have now the same problem as you had. i flashed accidentally the wrong firmware file for my op3t and it stucks now at the oneplus booting screen. how did you solved your issue back then? any help is appreciated.
the solution for my problem is to flash the correct firmware via pc - but i dont know how..
mcdachpappe said:
hey @M3drvr,
i have now the same problem as you had. i flashed accidentally the wrong firmware file for my op3t and it stucks now at the oneplus booting screen. how did you solved your issue back then? any help is appreciated.
the solution for my problem is to flash the correct firmware via pc - but i dont know how..
Click to expand...
Click to collapse
With the unbrick tool in the general section.
Hello everyone :laugh:!
Tried rooting the Nokia 4.2, did not know which img to use exactly so I tried one from some other shady site and messed up. Luckily, the recovery partition was still working. After trying to boot lots of images, I got tired and accidentally even flashed a Nokia 6.2 TWRP image to my recovery partition. Then I completely messed up. The phone only gets into fastboot now. May I please ask some help of you? I've been trying for days to fix things. I just wanted to root the original firmware. Now when I try to flash TWRP, it even says that the 'recovery' partition has no partition table! I can still write to boot_a and boot_b though. The phone originally had the October patch level, but before bricking it I upgraded it to the December level.
Kind regards,
Alexander47u
Search on google and try do download and flash the stock firmware (unrooted)
Phone does not get detected by QFIL
thegamingcat13 said:
Search on google and try do download and flash the stock firmware (unrooted)
Click to expand...
Click to collapse
I have tried this using QFIL, however the phone is not detected. The phone also goes into fastboot as soon as the cable is plugged in, even when the phone is off.
Have also installed appropiate drivers for QFIL, but no luck.
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Works, Thank you!
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Thank you! This worked flawlessly.
#metoo
Haha, I have done the EXACT same thing as you. Now I can only enter fastboot mode and when I try to flash anything I have downloaded I get an error about missing partitions. I have looked everywhere for details on the partition sizes, mount points and so on but nobody has uploaded the information. In the end I went and purchased a second device in order to dump the entire stock ROM in order to fix the first phone. I've got the second phone running in ADB-mode but I can only backup to an .ab file so now I am back at square one. All of the guides I can find on how to dump the ROM involves flashing TWRP recovery but THERE IS NONE FOR THE 4.2 :crying: And after researching Android forensics I have found a guide to dumping the ROM but it needs root access in the phone shell. All I wanted was root (and LineageOS). Does anyone feel like patching the stock ROM and making a zip-file containing the img-files from all of the partitions?
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
alexander47u said:
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
Click to expand...
Click to collapse
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
alexander47u said:
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
Click to expand...
Click to collapse
I was able to succesfully patch boot.img with magisk, then I copied the patched boot image to my computer with linux. Fastboot flash boot boot.img worked but upon reboot I got an error message saying "corrupt data" and offered to do a factory reset. Any chance you can upload your patched boot image so I can use yours?
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Posted
alexander47u said:
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Click to expand...
Click to collapse
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Oslokalle said:
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Click to expand...
Click to collapse
Up to March. I used the stock rom that is floating around on the internet. Not sure if I am allowed to post stock roms.
I was able to update to April using Magisk but not any further than that.
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Tried this using a user_update.zip file from www[.]getdroidtips[.]com/stock-rom-nokia-4-2-firmware/. My phone boots again, but Wi-Fi doesn't work. My model # is TA-1133. What should I do?
Edit: tried to install the latest security OTA from t[.]me/nokiarepoen/379, V2.29C, but I get
Code:
E:Package is for source build 00WW_2_29B but expected 00WW_1_17I
. Is there a base user_update for build 00WW_2_29B floating around?
Oslokalle said:
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
Click to expand...
Click to collapse
Kindly provide me that zip too.