Related
Has anyone got, or able to flash for me, the boot.img from stock N2506EX_23_150108?
Many gratitude points if you could upload for me ?
Thanks.
2nd
babelmonk said:
Has anyone got, or able to flash for me, the boot.img from stock N2506EX_23_150108?
Many gratitude points if you could upload for me
Thanks.
Click to expand...
Click to collapse
Hey I am also looking for this....on a side note are you looking for this because of wifi issues? has anyone found a fix?...pretty bummed wifi is not working on this thing
Could you install the dumps in http://forum.xda-developers.com/oppo-n3/help/looking-dump-boot-img-t2998030 Post #5, then unroot and run the OTAs to get you back up to current?
...
Lum_UK said:
Could you install the dumps in http://forum.xda-developers.com/oppo-n3/help/looking-dump-boot-img-t2998030 Post #5, then unroot and run the OTAs to get you back up to current?
Click to expand...
Click to collapse
I doubt that any stock rom will flash with twrp recovery....in the past with oppo phones (n1, 7a) its always needed stock recovery to flash stock roms...I guess we just play the waiting game until someone can upload the boot image from the updated rom. I'm pretty sure flashing that alone will get wifi back up and running. 07 Or if someone has the stock recovery they could upload....I am unsure if you can just rip it directly out of the rom and flash it....Also on oppo forums they have posted the rom for 5207 I am also unsure if you can flash that to the 5206.
The zip in that thread is images to flash in fastboot?
...
I would think you would have to flash each image individually.... system, boot, recovery ....unless if we start by flashing only the unmodified boot.img to see if it will fix wifi....but i doubt it because i suspect the wrong boot image is what screwed up wifi in the first place...someone please correct me if im wrong
c0dysm1th said:
I would think you would have to flash each image individually.... system, boot, recovery ....unless if we start by flashing only the unmodified boot.img to see if it will fix wifi....but i doubt it because i suspect the wrong boot image is what screwed up wifi in the first place...someone please correct me if im wrong
Click to expand...
Click to collapse
Yes, you're right; the boot image is not compatible with the upgrade; so downgrade to get root. I'm working on trying to upgrade again with the OTA upgrade and then getting the new boot.img and rooting that. More soon I hope!
FYI I tried your images, Lum_UK and found that I couldn't flash boot.img with fastboot, BUT I could dd them from within recovery, so I got myself up and running again.
Yes you'd have to flash all the images by hand one after the other.
edit: Replied before seeing babelmonk's response, please ignore this post.
steps?
babelmonk said:
Yes, you're right; the boot image is not compatible with the upgrade; so downgrade to get root. I'm working on trying to upgrade again with the OTA upgrade and then getting the new boot.img and rooting that. More soon I hope!
FYI I tried your images, Lum_UK and found that I couldn't flash boot.img with fastboot, BUT I could dd them from within recovery, so I got myself up and running again.
Click to expand...
Click to collapse
Can u please list the steps u took I'd like to get back up and running but don't want to screw this phone up any more ....(dd from recovery ) I'm not familiar with this if it is a command
babelmonk said:
Yes, you're right; the boot image is not compatible with the upgrade; so downgrade to get root. I'm working on trying to upgrade again with the OTA upgrade and then getting the new boot.img and rooting that. More soon I hope!
FYI I tried your images, Lum_UK and found that I couldn't flash boot.img with fastboot, BUT I could dd them from within recovery, so I got myself up and running again.
Click to expand...
Click to collapse
I can't get the OTA to work even after downgrading, but I do have a working system running 141228 with that hacked kernel, root and non-broken wireless.
Anyone want a nandroid of it? It's a slight upgrade at least
please
Lum_UK said:
I can't get the OTA to work even after downgrading, but I do have a working system running 141228 with that hacked kernel, root and non-broken wireless.
Anyone want a nandroid of it? It's a slight upgrade at least
Click to expand...
Click to collapse
please hook it up with that nandroid that i can flash in twrp
c0dysm1th said:
please hook it up with that nandroid that i can flash in twrp
Click to expand...
Click to collapse
Here you go, sorry it's taken so long
http://lum.uk/n3/files/N5206EX_23_141228_root_nocd.7z
Extract it into the TWRP backups folder and then restore like any other nandroid.
THANK YOU
Lum_UK said:
Here you go, sorry it's taken so long
http://lum.uk/n3/files/N5206EX_23_141228_root_nocd.7z
Extract it into the TWRP backups folder and then restore like any other nandroid.
Click to expand...
Click to collapse
Thank you how can i buy you a beer paypal?
c0dysm1th said:
Thank you how can i buy you a beer paypal?
Click to expand...
Click to collapse
Don't worry about it
Seems there's only about 4 or 5 people actively working on this phone here, so I'm sure we'll all end up helping each other at some point.
Lum_UK said:
Here you go, sorry it's taken so long
http://lum.uk/n3/files/N5206EX_23_141228_root_nocd.7z
Extract it into the TWRP backups folder and then restore like any other nandroid.
Click to expand...
Click to collapse
Thanks for that, though I haven't tried it yet. Can I ask what it changes? Is it worth the upgrade? My original firmware +root seems to work pretty well already so I may well leave it alone until L or CM comes out.
babelmonk said:
Thanks for that, though I haven't tried it yet. Can I ask what it changes? Is it worth the upgrade? My original firmware +root seems to work pretty well already so I may well leave it alone until L or CM comes out.
Click to expand...
Click to collapse
I have no idea what it changes as it's the firmware my International N5706 was shipped with when it was released last week. It may be different to the US model (though I believe the only difference between the two is the baseband) and is definitely different to the N5707 for Chinese users.
Dude, thanks!!! You saved my life!
I got wifi back AND root!
sivxo said:
I got wifi back AND root!
Click to expand...
Click to collapse
Hi ! when the zip file is downloaded, what is steps to install it please ?
thanks
marakud said:
Hi ! when the zip file is downloaded, what is steps to install it please ?
thanks
Click to expand...
Click to collapse
Sorry. Missed this. Did you manage?
Oppo neo 7 a33f custom recovery plzzz send me
Hello Everyone. I'm trying to downgrade the software on my Asus Zenfone 2 to version 2.19.40.20 (currently 2.19.40.20) so I can unlock my bootloader. I've heard that the way to do this is following rooting procedure 1 from the main information thread but flashing the version of the files that you want your system to be. However when I download the zip it has the system.img file broken up in some weird way (apparently you need a tool called WinRar to put it back together again but I really don't want to have to go buy a piece of software I'm only gonna need once). Does anyone know how to put the files back together again, have a put together 2.19.40.20 system.img I can use or have some alternative solution to my problem. I'm currently using a Linux system too so if at all possible I would like for any software to be compatible with Linux. If anyone has any insight I would be highly appreciative.
Don't try to flash selectively, as that is very likely to brick your phone. What you want is the correct full ROM package containing a system.img, boot.img/kernel, fastboot (droidboot.img IIRC), IFWI.zip, and some other important partitions whose names escape me. Don't try to extract parts of it (e.g. just the system.img, boot.img, or bootloader), because the components appear to be interdependent. In particular, flashing the wrong version of the bootloader without flashing the corresponding kernel/system image will more than likely brick it. You should be able to supply the full ROM to fastboot (e.g. fastboot update <package_file>). Double check everything and back up before you proceed! @Tuanies should have some pointers for you in case I missed anything, and I would wait to hear from him before you try this.
WinRAR is free. It's a very small program that takes seconds to download and install. It is very simple to put the system image components back together with WinRAR and then you will have that file plus the other three you need. Please try it, I'm sure you'll manage it.
All I suggest is to get the full firmware of 2.19.40.20 and flash the images one by one, and sideload the firmware using adb...
Hope this helps
Good luck.
I'd just download the full package from that's ~1GB and sideload that via recovery in its entirety. If this is too complicated, I'd advise against attempting it.
Seriously it is just about writing 3 lines on adb... Not that hard
Sent from my ASUS_Z008D using Tapatalk
I did finally manage to get WinRar working. I had to go install it on my brother's computer. After I had the files to flash I had no trouble.
This seems like a good place to ask this I was on .22 and tried unlocking boot loader did not seem to work so I went back into my 2.19 folder and flashed back to 2.19 but was still unable to unlock though it appears possibly unlocked on boot loader shows bootloader unk and question marks on last 2 entries, but apparently I am unable to flash over the bootloader in fastboot it says fail cmd err can anyone tell me what that means? And how to get around it, tried flashing non tethered twrp says it wrote it but won't boot to it
Sent from my ASUS_Z00AD using Tapatalk
You must have done something wrong. I had the two question marks before I unlocked mine. When your bootloader is unlocked your boot screen will be white. If you're not sure what I'm talking about then you're not unlocked.
robopilot99 said:
You must have done something wrong. I had the two question marks before I unlocked mine. When your bootloader is unlocked your boot screen will be white. If you're not sure what I'm talking about then you're not unlocked.
Click to expand...
Click to collapse
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
---------- Post added at 06:09 PM ---------- Previous post was at 05:58 PM ----------
jimchee said:
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
Click to expand...
Click to collapse
The img's I am flashing are from shakalaka, hope thats spelled right
so in fastboot and using adb i did fastboot flash droidboot droidboot.img (enter)
sending droidboot (14410 kb)
Okay (0.622s)
writing "droidboot"
FAILED < Remote: flash_cmds error !
so this is the answer I am getting when trying to flash droidboot
so any ideas would be great
jimchee said:
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
---------- Post added at 06:09 PM ---------- Previous post was at 05:58 PM ----------
The img's I am flashing are from shakalaka, hope thats spelled right
so in fastboot and using adb i did fastboot flash droidboot droidboot.img (enter)
sending droidboot (14410 kb)
Okay (0.622s)
writing "droidboot"
FAILED < Remote: flash_cmds error !
so this is the answer I am getting when trying to flash droidboot
so any ideas would be great
Click to expand...
Click to collapse
I had to flash 4 files as it appears you are trying to do. The error is definitely not good. I'm not sure what it means though. Hopefully someone else knows what to do. I'm pretty sure being on this up to date bootloader is your issue. Did you manage to somehow flash the other 3 files?
robopilot99 said:
I had to flash 4 files as it appears you are trying to do. The error is definitely not good. I'm not sure what it means though. Hopefully someone else knows what to do. I'm pretty sure being on this up to date bootloader is your issue.
Click to expand...
Click to collapse
Yep I figure that might be it, just not sure what to do next, every other file flashes whether I am going up or down thinking of trying to flash older than 19 and then hopefully able to its to 2.19, but hopefully someone knows the proper way
Sent from my ASUS_Z00AD using Tapatalk
The files that I flashed I got from here. Don't know if that's where you are getting yours.
What I did is I downgraded to version Z00A_WW_2.19.40.18 of everything (I was warned about flashing different versions of different things so be careful). I then used the bootloader unlock method detailed in section 5 of the resource thread. I think your problem is that the files you are flashing are not pre-rooted. I used the files from section 3.1, method 1 of the same thread. The system.img was broken up in some strange fashion but I can send you the put together version somehow if you would like.
robopilot99 said:
What I did is I downgraded to version Z00A_WW_2.19.40.18 of everything (I was warned about flashing different versions of different things so be careful). I then used the bootloader unlock method detailed in section 5 of the resource thread. I think your problem is that the files you are flashing are not pre-rooted. I used the files from section 3.1, method 1 of the same thread. The system.img was broken up in some strange fashion but I can send you the put together version somehow if you would like.
Click to expand...
Click to collapse
I am using the pre rooted ones from shakalaka and i can get boot, recovery and system to flash but unable to get droidboot to flash and that is what I can't figure out even when i downgrade with all the other files i can't get bootloader unlocked
I couldn't find the files you were referring too. However I really don't know enough about fastboot to really help you resolve the error message. Hopefully someone a little more experienced will come along soon.
robopilot99 said:
I couldn't find the files you were referring too. However I really don't know enough about fastboot to really help you resolve the error message. Hopefully someone a little more experienced will come along soon.
Click to expand...
Click to collapse
They are the same files that you are using from mega.nz and my fastboot knowledge is not great either, so I'll just wait around and see if anyone with more knowledge can help me out, thanks for yoyr help though it's appreciated
@jimchee you are typing the wrong command to flash droidboot. its "fastboot flash fastboot droidboot.img"
Niropa said:
@jimchee you are typing the wrong command to flash droidboot. its "fastboot flash fastboot droidboot.img"
Click to expand...
Click to collapse
Thanks Niropa, I knew there was reason this works now I really appreciate the help
Just a quick note to let everyone know that everything worked without a hitch now have unlocked bootloader and twrp installed.
Sent from my ASUS_Z00AD using Tapatalk
Went through the whole process to get an unlocked phone working on verizon - unlock bootloader, TWRP, s-off, etc.
Went back and flashed stock 1.21 recovery since that's what my phone was on, did a factory reset after getting this error the first time.
Still getting the error -
Code:
Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance.
Before flashing the stock recovery I did try to restore the recovery/system image from TWRP's system backup, not sure if that has anything to do with it.
noahjk said:
Went through the whole process to get an unlocked phone working on verizon - unlock bootloader, TWRP, s-off, etc.
Went back and flashed stock 1.21 recovery since that's what my phone was on, did a factory reset after getting this error the first time.
Still getting the error -
Code:
Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance.
Before flashing the stock recovery I did try to restore the recovery/system image from TWRP's system backup, not sure if that has anything to do with it.
Click to expand...
Click to collapse
Try flashing this zip in download mode (fastboot flash zip pathtozip.zip)
https://drive.google.com/file/d/0B8OH6sFjVE1ld1ptNTFEaEc3Rms/view?usp=docslist_api
Reboot and try ota again.
This will flash the unlocked radio though, so you'll need to reperform the steps from the Verizon thread after you do this. please report back if it works.
jollywhitefoot said:
Try flashing this zip in download mode (fastboot flash zip pathtozip.zip)
https://drive.google.com/file/d/0B8OH6sFjVE1ld1ptNTFEaEc3Rms/view?usp=docslist_api
Reboot and try ota again.
This will flash the unlocked radio though, so you'll need to reperform the steps from the Verizon thread after you do this. please report back if it works.
Click to expand...
Click to collapse
Worked great. Thanks!
For anyone else following this thread, if you're flashing the zip and see this:
Code:
remote: 90 hboot pre-update! please flush image again immediately
Just flash again right away and it'll work fine.
noahjk said:
Worked great. Thanks!
For anyone else following this thread, if you're flashing the zip and see this:
Code:
remote: 90 hboot pre-update! please flush image again immediately
Just flash again right away and it'll work fine.
Click to expand...
Click to collapse
I'm glad that worked for you. I went ahead and wrote a guide in case anyone else has trouble. It includes the message about reflashing.
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
international version
jollywhitefoot said:
Try flashing this zip in download mode (fastboot flash zip pathtozip.zip)
Reboot and try ota again.
This will flash the unlocked radio though, so you'll need to reperform the steps from the Verizon thread after you do this. please report back if it works.
Click to expand...
Click to collapse
Hey there, Ive come across your post after experiencing the same problem on a HTC10 international version. Can I ask if the file that you've provided work on the international version? Also do I have to restore my twrp backup as well? Thanks a lot!
Hi there, same problem: "Can't update software. There was an unexpected error and the file system may be corrupted. Please contact HTC support for further assistance."
Htc 10 unlocked, v. 1.90.401.5
I followed post #2 without success.
Some idea please?
Help, please! ?
I gave up with the same problem and switched to a custom rom - Leedroid.
Thank you Simplici. So no chance with official stock to solve this problem?
last_nooby said:
Thank you Simplici. So no chance with official stock to solve this problem?
Click to expand...
Click to collapse
There is. You could flash an appropriate RUU if available. Although it'll wipe all you're data, it should restore the phone to a status, making an OTA update possible again. Those errors could be caused by a once r/w mounted system partition, or a tripped dm-verity flag. You'll find more on this issues and help of how to properly restore over at the Guides section of this forum.
Edit: here's the link regarding the corrupt system partition error: http://forum.xda-developers.com/htc...o-ota-receive-corrupt-message-t3378187/page43
Sent from my htc_pmeuhl using XDA Labs
jollywhitefoot said:
Try flashing this zip in download mode (fastboot flash zip pathtozip.zip)
https://drive.google.com/file/d/0B8OH6sFjVE1ld1ptNTFEaEc3Rms/view?usp=docslist_api
Reboot and try ota again.
This will flash the unlocked radio though, so you'll need to reperform the steps from the Verizon thread after you do this. please report back if it works.
Click to expand...
Click to collapse
can some one reload the file again? there's no file in google drive
Solved my problem by flashing the FULL firmware and not only the boot.img !
Could a mod delete the thread please ? Thanks !
Pouni said:
Solved my problem by flashing the FULL firmware and not only the boot.img !
Could a mod delete the thread please ? Thanks !
Click to expand...
Click to collapse
How did you accomplish this? I can't get RSD Lite to detect my phone (although fastboot devices shows it listed) and I can't flash the full firmware via adb because I keep getting "Image not signed or corrupt". I'm really confused.
Pouni said:
Solved my problem by flashing the FULL firmware and not only the boot.img !
Could a mod delete the thread please ? Thanks !
Click to expand...
Click to collapse
Please don't ask mods to delete threads because of successful outcomes - post your solution instead. Leave the threads up as they are a useful resource for others (at least those who search before posting! )
Thanks
Sent from my SAMSUNG-SM-G920A using Tapatalk
joesee said:
How did you accomplish this? I can't get RSD Lite to detect my phone (although fastboot devices shows it listed) and I can't flash the full firmware via adb because I keep getting "Image not signed or corrupt". I'm really confused.
Click to expand...
Click to collapse
I kept getting the "Image not signed or corrupt" whenever I had to flash the boot.img but I ignored the error once to try and see if it had any positive outcome, and it worked fine !
Can't flash stock ROM, can you do a detail installation log?
Pouni said:
I kept getting the "Image not signed or corrupt" whenever I had to flash the boot.img but I ignored the error once to try and see if it had any positive outcome, and it worked fine !
Click to expand...
Click to collapse
Is ur bootloader unlocked or not??
If not try unlock ur bootloader than try it ll work
From what I can tell you will always get the "Image not signed or corrupt" error, but it works anyways. Idk why but it doesnt matter as long as it works . Motorola(Lenovo) has the instructions to flash stock firmware on your device, just download the firmware for your device and follow those instructions.
jon7701 said:
From what I can tell you will always get the "Image not signed or corrupt" error, but it works anyways. Idk why but it doesnt matter as long as it works . Motorola(Lenovo) has the instructions to flash stock firmware on your device, just download the firmware for your device and follow those instructions.
Click to expand...
Click to collapse
Jon, can you help me? already tried to flash stock rom in fastboot but it doesn't flash.... i'm tired of this
Vitxlss said:
Jon, can you help me? already tried to flash stock rom in fastboot but it doesn't flash.... i'm tired of this
Click to expand...
Click to collapse
Did you only flash the stock rom or did you try to flash everything? If you didnt try to flash everything I would try that and make sure you have the correct stock firmware for your device before you do that. Theres not really much else you can do other than try flashing in twrp, but idk if twrp supports space chunks, but it does support images. If it really comes down to it, you can force flash the system partition in twrp, but you would need the whole system image and not space chunks.
If you made a mistake like doing fastboot flash boot init_boot
You have a bad boot now or boot loop, the solution is
Flash Boot files of the exact running OS version from fastbootD
This will fix the issue
I have extracted this from the partition backup application hopefully it will work for you
Boot Files below
Can you access fastboot? If not, it's hard bricked. You need to goto service centre or Get it flashed remotely by paying someone.
surajpai524 said:
Can you access fastboot? If not, it's hard bricked. You need to goto service centre or Get it flashed remotely by paying someone.
Click to expand...
Click to collapse
I can access fastboot and recovery
I need A10 least fraimware boot.img and init Boot and I think flashing this Will work
ahasae said:
I can access fastboot and recovery
I need A10 least fraimware boot.img and init Boot and I think flashing this Will work
Click to expand...
Click to collapse
did you get a full zip rom by chance? idk why it's so hard to find one or why Oneplus doesn't offer downloads from their site anymore....
What i find funny is that by following that guide 100% would have you up and running with root. This tells me following directions is hard to since we can only give directions and hope you can following them. Reading the full guide before proceeding with it. Step 6: BOOT the kernel. DO NOT EVER FLASH THIS PHONE!
SourPower said:
did you get a full zip rom by chance? idk why it's so hard to find one or why Oneplus doesn't offer downloads from their site anymore....
Click to expand...
Click to collapse
https://oxygenos.oneplus.net/6160_sign_CPH2451_11_A_OTA_0090_all_FVA3Ps_10100001_2.zip
I think this one
I am using version 2451, but I can not update to 13.1. Can you give me an answer?
gunzpro21 said:
I am using version 2451, but I can not update to 13.1. Can you give me an answer?
Click to expand...
Click to collapse
Try with oxygen updater app