Related
This is the discussion thread for firmware.mobi.
This site replaces my old central CF-Auto-Root repository, and aside from letting you create and download CFARs, also lets you download stock boot and recovery images for many firmwares and view all sorts of information about them.
Initial publication post: https://plus.google.com/+Chainfire/posts/YzfaWH1KDG8
--- reserved ---
--- also reserved ---
I honestly don't know how you find the time! Your dedication to the community is phenomenal.
Many will welcome this from noobs to devs. I know I'll find it handy in my endeavours.
Thanks.
Sir
If you want a great repository on the stock firmware of the various brands then you may refer to needrom.com which I think is according to me as a great repository of the stock firmwares and the boot images can be extracted from their.
i don't know what to say
i don't know what to say , things we can do is to donate chainfire i will send my contribution because you take a huge times to help us and we want to thank you by not saying "only thanks" but donate "money".one more times thank you
This is awesome!! Thanks for the hard work it's just amazing. I've been checking it out and I'm getting a hot linking disabled error. And clicking on the following link does nothing. Am I doing something wrong?? Trying to configure a c.f. root package for my sm-g950w. Any ideas guys??
thatsupnow said:
This is awesome!! Thanks for the hard work it's just amazing. I've been checking it out and I'm getting a hot linking disabled error. And clicking on the following link does nothing. Am I doing something wrong?? Trying to configure a c.f. root package for my sm-g950w. Any ideas guys??
Click to expand...
Click to collapse
Try using Chrome or Firefox. Seems to be an issue with IE/Edge. I'll check this out later.
Chainfire said:
Try using Chrome or Firefox. Seems to be an issue with IE/Edge. I'll check this out later.
Click to expand...
Click to collapse
Another question, I see that the 950w firmware is from May, if I uploaded the newest firmware would you be able to add that in??
Edit: works on chrome but not Firefox or IE
Chainfire said:
This is the discussion thread for firmware.mobi.
This site replaces my old central CF-Auto-Root repository, and aside from letting you create and download CFARs, also lets you download stock boot and recovery images for many firmwares and view all sorts of information about them.
Initial publication post: https://plus.google.com/+Chainfire/posts/YzfaWH1KDG8
Click to expand...
Click to collapse
I have attempted time and time again, even with your new site, but i cant get CF Auto Root to work on my Samsung Galaxy J3 (2017) SM-J327T and my Galaxy J7 (2017) SM-J727T. They are both coming back with SECURE CHECK FAIL (RECOVERY). Others Methods i have tried failed for SECURE CHECK FAIL (Cache) which i was told meant Locked Bootloader. That being the case, why is Recovery failing on your root method.
If it is a Locked Bootloader on both devices, if there a way around this?
Thank you in advance!
DeviceManagent said:
I have attempted time and time again, even with your new site, but i cant get CF Auto Root to work on my Samsung Galaxy J3 (2017) SM-J327T and my Galaxy J7 (2017) SM-J727T. They are both coming back with SECURE CHECK FAIL (RECOVERY). Others Methods i have tried failed for SECURE CHECK FAIL (Cache) which i was told meant Locked Bootloader. That being the case, why is Recovery failing on your root method.
If it is a Locked Bootloader on both devices, if there a way around this?
Thank you in advance!
Click to expand...
Click to collapse
This has already been explained to death. Chainfire even reiterates it on the new website.
Binaries, that includes recovery and boot images, that are not signed by Samsung CANNOT be flashed on a bootloader locked device, period.
No matter what the method.
Firmware.mobi doesn't add some new magic that can bypass bootloaders. It's simply an automated process.
It still stands that if your device has a locked bootloader it simply will not work.
Wow... Thanks for the hardwork.
Trying to generate for A9pro A910F 7.0 but failed. The only setting that i know for qualcom is to set cache image as ext4 type. After flash with odin internal storage corrupted. Need help for actual setting regarding the encryption.
@ Chainfire: Hi Sir: thanks for your great efforts to help the android community, really appreciated! i have generated cfar_google_pixel-xl_marlin_opr1.170623.026_t1.zip for Pixel XL. I want to root, can I just flash this zip file, or do I still need to flash the SuperSu as well? Could you please outline the steps? What's the best use of CF-Auto-Root zip file from firmware.mobi? Thank you!
Hi, ive been trying to upload zips of the Nvidia Shield, OnePlus 3 etc, however it keeps giving an error and I am not able to upload it.
The error is
Secure Connection Failed
The connection to the server was reset while the page was loading.
This happens in Edge, Chrome, Opera, and Firefox.
Uploaded Files and waiting for status
Hii sir!
I have uploaded Stock images of Boot,Recovery & Cache of my device which is Lenovo Vibe K5 Note.How can i know the status of my files being processed? Please reply.
rkchandra041 said:
Hii sir!
I have uploaded Stock images of Boot,Recovery & Cache of my device which is Lenovo Vibe K5 Note.How can i know the status of my files being processed? Please reply.
Click to expand...
Click to collapse
Does CF-AUTOROOT even work on Lenovo devices?
VanGolfer said:
@ Chainfire: Hi Sir: thanks for your great efforts to help the android community, really appreciated! i have generated cfar_google_pixel-xl_marlin_opr1.170623.026_t1.zip for Pixel XL. I want to root, can I just flash this zip file, or do I still need to flash the SuperSu as well? Could you please outline the steps? What's the best use of CF-Auto-Root zip file from firmware.mobi? Thank you!
Click to expand...
Click to collapse
Extract the ZIP, instructions inside...
It does install SuperSU.
Though you say 'flash this zip', which implies you have TWRP, in which case you can just flash the SuperSU ZIP and don't need CF-Auto-Root.
eyeoflucifer said:
Hi, ive been trying to upload zips of the Nvidia Shield, OnePlus 3 etc, however it keeps giving an error and I am not able to upload it.
The error is
Secure Connection Failed
The connection to the server was reset while the page was loading.
This happens in Edge, Chrome, Opera, and Firefox.
Click to expand...
Click to collapse
How big are the firmwares?
Can you put one of them on drive and link it to me so I can test if it has something to do with the firmware images itself?
rkchandra041 said:
Hii sir!
I have uploaded Stock images of Boot,Recovery & Cache of my device which is Lenovo Vibe K5 Note.How can i know the status of my files being processed? Please reply.
Click to expand...
Click to collapse
It normally redirects to a queue page after the upload which shows you the status... what happeend? did it just redirect to the same page again?
How big are the firmwares?
Can you put one of them on drive and link it to me so I can test if it has something to do with the firmware images itself?
Click to expand...
Click to collapse
here you go.
https://drive.google.com/open?id=0B0wyPrkY34xAcElCZU1CN3FzRnc
..
eyeoflucifer said:
here you go.
https://drive.google.com/open?id=0B0wyPrkY34xAcElCZU1CN3FzRnc
Click to expand...
Click to collapse
Max upload size issue on the server. Should be fixed now. I uploaded the nvidia one, you can do the OP3 one
Still, it would be better to extract the boot and recovery images, then zip those up.
I'm sure there are other posts like this will be. I know - I've read probably all of them. But I am still stuck.
MHA-L29C636 phone. I rooted last night and when I was setting my apps back up, I noticed Snapchat wasn't working. A quick search told me to install XPosted Framework. I downloaded and installed it, and shortly after that, if not immediately, my phone shut off and wouldn't start.
I was at work, so I panicked. Thankfully, the eRecovery thing booted up and told me I could reinstall over WiFi. GREAT! Nope. It was not able to connect to the server. I tried a few times, reset. A few more, reset. Different network, reset.... Nothing was working. So, I did a data wipe and selected Dalvik Cache, Data, Internal Storage, Cache, System partition, and then did a factory reset. I figured that could clear out the XPosted install and I would start fresh. No, that also did not work...
So, I've searched for 6 hours since I've gotten home from work, tried countless methods and downloaded almost 20GB of images, custom ROMS, firmware files, etc. And LITERALLY almost 20GB. I keep running into issue after issue preventing me from getting anything to work.
I've installed ADB/Fastboot. That wasn't working, so I installed the full Android Studio and SDK Toolkit. Didn't get anywhere with Fastboot.
I've tried flashing custom ROM's to get SOMETHING back on my phone. Nothing will install.
I've tried doing a forced update with the POWER + VOL UP + VOL DOWN. Did not work. Gives an error of unable to update.
Then I came across HWOTA. The write ups were confusing as hell to me... but finally I understood one. Copied the 3 files to the SD card to load into the phone and went to run update.bat from the HWOTA extracted folder..... Except the batch file instantly closes and I don't get to see the screen with the numbers that EVERYONE else gets to see apparently.
HiSuite doesn't even see the phone.
I'm completely lost. I need some help. Badly.
@mankindtw I've seen hundreds of your posts. You seem pretty in the know with the Mate 9
http://www.carbontesla.com/2017/05/tutorial-rebrand-convert-huawei-mate-9-to-any-region/
https://forum.xda-developers.com/mate-9/how-to/guide-how-to-unbrick-mate-9-access-t3720953
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I was following these guides for the HWOTA procedure, and as I said, the update.bat will not execute. "...is not recognized as an internal or external command,
operable program or batch file." is the message that is created.
https://www.getdroidtips.com/huawei-mate-9-b321-oreo-firmware/
I downloaded my firmware files from here, as well as the page here on XDA.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page26
Then I came across this man showing me what I can't see with update.bat. >.>
Hopefully someone can help quickly. I'm tired of messing with this phone and I'm needing it for this weekend.
What Android's version did you have? Nougat or Oreo?
If Nougat there is quick method to unbrick.
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
Just do option 4 - download special service ROM for your region C636 and apply it via dload.
If your phone will boot and has no system update, then do options with installing TWRP and additional package. System update will appear and you will have ability to get new ROM.
P.s. I don't know does this method work in case with Oreo's "brick". It did not tested.
5[Strogino] said:
What Android's version did you have? Nougat or Oreo?
If Nougat there is quick method to unbrick.
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
Just do option 4 - download special service ROM for your region C636 and apply it via dload.
If your phone will boot and has no system update, then do options with installing TWRP and additional package. System update will appear and you will have ability to get new ROM.
P.s. I don't know does this method work in case with Oreo's "brick". It did not tested.
Click to expand...
Click to collapse
Unfortunately, it just updated to O last week. I'm wondering if that's why the eRecovery does not work as it should.
I don't know enough about the file structure of Huawei to be able to know how to reload everything back into place, brand new. I'm familiar with Samsung and Odin, but I'm trying to find out the steps for getting everything squared away.
I also realized that I'm not 100% certain that this had the C636 FW. It's a dual SIM and I believe I bought the International version instead of the US version. Would it be best to rebrand to a specific region so I at least know what it's set up for?
What is the correct process for re-flashing the file structure and files? I'd imagine what I need to do is a full format, and then reload everything from the ground up. I just don't know the correct order. Re-brand, flash new UPDATE.APP and the 3 zip files? Would I force flash the UPDATE.APP and then flash zip through TWRP?
I've thought about cutting my losses and trying out this FunkyHuawei thing, that's just a good bit of money I was not prepared to be spending, and especially for no guaranteed result. I was not looking to mod this phone at all, just root access for some monitoring apps.
I may see what an authorized service center will charge to fix it. I'd hate to keep tinkering with it and get it hard bricked.
Why don't you try FunkyHuawei? You have to buy credits though... https://funkyhuawei.club/
gioarvdv said:
Why don't you try FunkyHuawei? You have to buy credits though... https://funkyhuawei.club/
Click to expand...
Click to collapse
I had said above that it was a lot of money to invest in something not guaranteed to work. At least if I brought it to a shop, I wouldn't pay unless it were fixed.
300zxmatt said:
I had said above that it was a lot of money to invest in something not guaranteed to work. At least if I brought it to a shop, I wouldn't pay unless it were fixed.
Click to expand...
Click to collapse
I think the reason your .bat file doesn't work is where you have it placed. I had the howta folder on my desktop and it wouldn't work not matter what I did. I moved it to the root of the c:// drive and then it worked. Perhaps you should try that.
Mmm... I have to just saying: stop killing phone!
Why you are thinking that format system will help? It will kill your system partition and you will get no ability to run into normal mode anymore. Without system partition phone will not run.
Why are you thinking that rebranding will help you? You have troubles with current region. You will feed the mess while rebranding cause it will get additional troubles with metadata mismatch.
Your current goal is to get phone when it is running normal. To do that, you can apply service ROM. Service ROM is special one, it is only ROM that can be flashed via dload. Other ROMs can not be flashed this way.
5[Strogino] said:
Mmm... I have to just saying: stop killing phone!
Why you are thinking that format system will help? It will kill your system partition and you will get no ability to run into normal mode anymore. Without system partition phone will not run.
Why are you thinking that rebranding will help you? You have troubles with current region. You will feed the mess while rebranding cause it will get additional troubles with metadata mismatch.
Your current goal is to get phone when it is running normal. To do that, you can apply service ROM. Service ROM is special one, it is only ROM that can be flashed via dload. Other ROMs can not be flashed this way.
Click to expand...
Click to collapse
Alright, I downloaded that offline firmware dload zip, extracted it on my SD card all alone, and tried installing. It gave a "Software Install Failed" message just like the other times.
https://forum.xda-developers.com/showthread.php?t=2277112
Following this to get a better understanding of Fastboot and how to use it.
I tried 'fastboot erase system -w' and it returned with
"wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'system'...
OKAY [ 46.028s]
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.358s]
finished. total time: 46.388s"
That first bit about being unable to determine the partition type worries me a little bit. That is why I was talking about re-wiping everything and starting from scratch @5[Strogino]
Wow. I booted into TWRP and went to do the factory reset through there and it threw an error for every operation. I have a feeling that trying more things is doing more harm than good.
Edit: found out how to fix that. I went to Wipe>Advanced Wipe>Selected 'System'>'Repair or Change'> and opted for EXT4 because apparently that is the most common.
300zxmatt said:
Wow. I booted into TWRP and went to do the factory reset through there and it threw an error for every operation. I have a feeling that trying more things is doing more harm than good.
Edit: found out how to fix that. I went to Wipe>Advanced Wipe>Selected 'System'>'Repair or Change'> and opted for EXT4 because apparently that is the most common.
Click to expand...
Click to collapse
Dude you're really just making **** worse by throwing the everything and the kitchen sink at it. Inbox me or something so we can have a conversation as to your options
I agree...
shae23 said:
I think the reason your .bat file doesn't work is where you have it placed. I had the howta folder on my desktop and it wouldn't work not matter what I did. I moved it to the root of the c:// drive and then it worked. Perhaps you should try that.
Click to expand...
Click to collapse
the reason why the Batch file instantly closes is due to where you have saved it. Move it to C:\ and you should be good to go. HWOTA is by far the best method to recover your phone (in my opinion)....and even better....it's free!
rbt001 said:
the reason why the Batch file instantly closes is due to where you have saved it. Move it to C:\ and you should be good to go. HWOTA is by far the best method to recover your phone (in my opinion)....and even better....it's free!
Click to expand...
Click to collapse
Well! That got me somewhere! I never saw anywhere that I found to place it in the root directory of the drive. I guess since ADB is located there, it kind of makes sense?
Now, new issue. This is what I'm getting off the bat.
****************************************
* *
* This script is made by XDA mankindtw *
* *
****************************************
Use Vol-Dn + USB Cable to boot into fastboot mode.
Press ENTER key to continue...
Replace recovery to TWRP, please wait...
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.665s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.678s
Disconnect usb cable and turn off phone, use Vol-Up and Power key to enter TWRP recovery.
Press ENTER key to continue...
Click to expand...
Click to collapse
And after this failure, it will not do anything when I attempt to follow the prompt to boot and reconnect USB inside TWRP.
Any ideas from this point? Happy to have SOME amount of progress, and glad to be learning the correct procedure!
300zxmatt said:
Well! That got me somewhere! I never saw anywhere that I found to place it in the root directory of the drive. I guess since ADB is located there, it kind of makes sense?
Now, new issue. This is what I'm getting off the bat.
And after this failure, it will not do anything when I attempt to follow the prompt to boot and reconnect USB inside TWRP.
Any ideas from this point? Happy to have SOME amount of progress, and glad to be learning the correct procedure!
Click to expand...
Click to collapse
That's easy enough, do you have Twrp installed, if not, what was your last Android version, nougat or Oreo?
shae23 said:
That's easy enough, do you have Twrp installed, if not, what was your last Android version, nougat or Oreo?
Click to expand...
Click to collapse
Yes, I have TWRP installed prior to all of this. Most recent version was Oreo. I used the "twrp_android_o_mate9_a1" file to flash TWRP.
Under C:\HWOTA\recovery\MHA, I have 3 recovery versions. I'm assuming the script flashes "MHA_twrp-3.0.3-1-hi3660" judging my the returned file size and the file size in Windows for that file. I wonder if flashing it manually would fix the issue.
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
It´s just a preliminary build so I can´t promise anything/everything will work! Keep that in mind. I´m not responsible if you brick your device.
DOWNLOAD LINK:
https://drive.google.com/file/d/0B45...Eh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei...id_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you´ve got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don´t mess around too much with TWRP, to be sure you don´t brick your system!
Click to expand...
Click to collapse
I tried flashing the TWRP included in HWOTA and it err'd the same way. I'm assuming that like when I first installed TWRP and it didn't take the regular release, the version included and scripted with HWOTA is not compatible with O?
@mankindtw do you know anything about what my issue is with the script? TIA!
Here is the solution (forwad)
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei. This will also work for the Mate 10, Mate 10 Pro, Mate 10 Porsche and other EMUI 8 devices.
It´s just a preliminary build so I can´t promise anything/everything will work! Keep that in mind. I´m not responsible if you brick your device.
DOWNLOAD LINK:
https://drive.google.com/file/d/0B45...Eh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei...id_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you´ve got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don´t mess around too much with TWRP, to be sure you don´t brick your system!
Click to expand...
Click to collapse
I tried flashing the TWRP included in HWOTA and it err'd the same way. I'm assuming that like when I first installed TWRP and it didn't take the regular release, the version included and scripted with HWOTA is not compatible with O?
@mankindtw do you know anything about what my issue is with the script? TIA!
C:\Users\Matt\Downloads>fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (26982 KB)...
OKAY [ 1.045s]
writing 'recovery_ramdisk'...
OKAY [ 0.267s]
finished. total time: 1.314s
Click to expand...
Click to collapse
Flashing the O version above works fine.
My Phone Story.
I flashed custom ROM.
Later Flashed back to stock ROM but I mistakenly flashed to old STOCK ROM and updated the OTA UPDATE.
Phone bricked.
After unbricking phone, its baseband version changed and overall it became to Moto G4 only with no FP sensor working and 2nd IMEI lost. Baseband version was also changed to something else.
After reading a lot of threads on XDA, I found a solution which many people ain't gave. (maybe out of their mind.)
I was suggested to flash hw.img. But it didn't help.
Later a link is given to me by XDA member thanx @echo92 and @Tengakallan. But his info was less.
Later I found the solution by that link.
The following things I did is mention below.
FLASH AT YOUR OWN RISK
'---------------------------- PROCESS STARTS FROM HERE---------------------------------------
Hoping you have adb fastboot and latest firmware on your pc.
Install/Flash TWRP Recovery in your phone.
Download these files.
1 - modem.img ,
fsg.img
hw.img
2 - paste it into the adb folder and Open cmd/PowerShell here.
3 - Boot your phone into TWRP and execute the following codes in the cmd.
(Run the code containing hw.img at last. It doesn't matter if it executed first but that code will restart your phone while other two codes won't.)
Code:
adb push modem.img /dev/block/mmcblk0p1
adb push fsg.img /dev/block/mmcblk0p16
adb push hw.img /dev/block/mmcblk0p43
4 - After this, your phone will reboot and you can see two sim slots but it won't work as your baseband version will be "unknown".
Don't worry, the good news is that you got 2 IMEI back till here.
5 - Get the latest Firmware from XDA and reflash it. (See that you take the latest one.)
Your baseband version will change to its original.
6 - Dance like a Pro and hit Thanks to me..!
NOTE: - I tested it in MOTOROLA G4 PLUS - XT1643 - INDIA... I don't know other devices but can be tried rather than using the device like an iPod.
Good to hear you got your device working, where did you get the images from by the way?
At least this shows the (similar) process by lCrD512 still works for some users: https://forum.xda-developers.com/showpost.php?p=73977941&postcount=139
echo92 said:
Good to hear you got your device working, where did you get the images from by the way?
At least this shows the (similar) process by lCrD512 still works for some users: https://forum.xda-developers.com/showpost.php?p=73977941&postcount=139
Click to expand...
Click to collapse
Internet.
Just googled for "modem.img". I don't know the exact link but I read the thread and the person written that its file for almost all android devices.
I guess I have seen a word modem.img for all "Android Generic Devices" (you can search for this keyword)...
The site was not XDA though...!
You can check the file brother. I am not hacker/pro in these things.
Ya, I have seen that link you provided.
Also, I mentioned you in the above thread. But the drive link is no more working.
People like me who don't understand or first timers to deal with these things don't even know that there are modem.img and fsg.img missing.
Moreover, you said to flash hw.img only. Actually, modem.img also required.
echo92 said:
Good to hear you got your device working, where did you get the images from by the way?
At least this shows the (similar) process by lCrD512 still works for some users: https://forum.xda-developers.com/showpost.php?p=73977941&postcount=139
Click to expand...
Click to collapse
Okay I got the source for fsg.img file.
https://androidfilehost.com/?fid=745425885120709988
bonnyshroff said:
Okay I got the source for fsg.img file.
https://androidfilehost.com/?fid=745425885120709988
Click to expand...
Click to collapse
Hrm, there doesn't seem to be any indication whether it's for our devices. Without a source link, it's difficult to say what device it's even for.
Also, looking through the hex code for the modem.img you've uploaded, I see references to MediaTek CPUs:
Code:
[B]MTK_ROMINFO_v07[/B].ZTENJ77_CU_ICS2_PCB01_HSPA_[B]MT6577[/B]_S00.MAUI_11AMD_W12_22_SP_V1.BIN_FLNPF38F5060M0Y3DG...
So I'm really not sure if you've been lucky and the stock ROM repaired by flashing the fsg and modem meant for our devices or whether this process will work on other devices without creating more problems.
echo92 said:
Hrm, there doesn't seem to be any indication whether it's for our devices. Without a source link, it's difficult to say what device it's even for.
Also, looking through the hex code for the modem.img you've uploaded, I see references to MediaTek CPUs:
Code:
[B]MTK_ROMINFO_v07[/B].ZTENJ77_CU_ICS2_PCB01_HSPA_[B]MT6577[/B]_S00.MAUI_11AMD_W12_22_SP_V1.BIN_FLNPF38F5060M0Y3DG...
So I'm really not sure if you've been lucky and the stock ROM repaired by flashing the fsg and modem meant for our devices or whether this process will work on other devices without creating more problems.
Click to expand...
Click to collapse
Okay, Actually I am not pro as you (like you read that it's for MediaTek, I just applied for my phone) but I've seen the thread that it's for "ALMOST" all devices. Wait, lemme search again.
I searched my history but there are a lot of links to check.
bonnyshroff said:
Okay, Actually I am not pro as you (like you read that it's for MediaTek, I just applied for my phone) but I've seen the thread that it's for "ALMOST" all devices. Wait, lemme search again.
I searched my history but there are a lot of links to check.
Click to expand...
Click to collapse
It's not a question of being 'pro' or not - I'm just wanting to verify that, for a thread that is mentioning [SOLVED], that the files used in solving the issue are genuinely for our devices or at least compatible. We've seen many examples of files working for one user not working for another or worse, causing even more issues, and I'm just asking for verification as to the veracity. Like your posts, losing IMEI and SIMs means users can and will try anything. If it works for others including yourself, no issue. If it doesn't, we have to assist them and without knowing where the files came from, that makes it difficult.
As for the modem.img and fsg.img, that's a fair criticism and I apologise for not giving you the right advice (that you need modem.img and fsg.img as well).
echo92 said:
It's not a question of being 'pro' or not - I'm just wanting to verify that, for a thread that is mentioning [SOLVED], that the files used in solving the issue are genuinely for our devices or at least compatible. We've seen many examples of files working for one user not working for another or worse, causing even more issues, and I'm just asking for verification as to the veracity. Like your posts, losing IMEI and SIMs means users can and will try anything. If it works for others including yourself, no issue. If it doesn't, we have to assist them and without knowing where the files came from, that makes it difficult.
Click to expand...
Click to collapse
Okay Okay.
I found the links...
You can check it by yourself.
I even hope all of them get it helpful.
modem.img - https://forum.xda-developers.com/showthread.php?t=2525874
fsg.img - https://androidfilehost.com/?fid=745425885120709988
hw.img - https://forum.xda-developers.com/showpost.php?p=75534757&postcount=243
Okay bro, verify it...
A lot of people out there facing the problem like me.
echo92 said:
As for the modem.img and fsg.img, that's a fair criticism and I apologize for not giving you the right advice (that you need modem.img and fsg.img as well).
Click to expand...
Click to collapse
Ahh!, no worry friend...
At least you helped...
I guess I posted the thread with proper things. You can even recommend the changes
bonnyshroff said:
Okay Okay.
I found the links...
You can check it by yourself.
I even hope all of them get it helpful.
modem.img - https://forum.xda-developers.com/showthread.php?t=2525874
fsg.img - https://androidfilehost.com/?fid=745425885120709988
hw.img - https://forum.xda-developers.com/showpost.php?p=75534757&postcount=243
Okay bro, verify it...
A lot of people out there facing the problem like me.
Click to expand...
Click to collapse
Thanks for the links - at least other users can have an informed decision whether to flash them or not. I agree that there are a lot of users that are facing the issue through a bad stock ROM flash for example, I just don't want them to flash files without knowing where they're from and possibly making the situation worse.
As an aside, I've uploaded the hw.img, fsg.img and modem.img from my UK XT 1642 (EMEA baseband) - I have not tested these so as always, flash at your own risk: https://drive.google.com/drive/folders/1vQHJB37RV4Iv83jeO5mymw-UNe9KtRNm
echo92 said:
Thanks for the links - at least other users can have an informed decision whether to flash them or not. I agree that there are a lot of users that are facing the issue through a bad stock ROM flash for example, I just don't want them to flash files without knowing where they're from and possibly making the situation worse.
As an aside, I've uploaded the hw.img, fsg.img and modem.img from my UK XT 1642 (EMEA baseband) - I have not tested these so as always, flash at your own risk: https://drive.google.com/drive/folders/1vQHJB37RV4Iv83jeO5mymw-UNe9KtRNm
Click to expand...
Click to collapse
Thanx Bro..! :good:
Phone is not rebooting after the command is 100%
bonnyshroff said:
My Phone Story.
I flashed custom ROM.
Later Flashed back to stock ROM but I mistakenly flashed to old STOCK ROM and updated the OTA UPDATE.
Phone bricked.
After unbricking phone, its baseband version changed and overall it became to Moto G4 only with no FP sensor working and 2nd IMEI lost. Baseband version was also changed to something else.
After reading a lot of threads on XDA, I found a solution which many people ain't gave. (maybe out of their mind.)
I was suggested to flash hw.img. But it didn't help.
Later a link is given to me by XDA member thanx @echo92 and @Tengakallan. But his info was less.
Later I found the solution by that link.
The following things I did is mention below.
FLASH AT YOUR OWN RISK
'---------------------------- PROCESS STARTS FROM HERE---------------------------------------
Hoping you have adb fastboot and latest firmware on your pc.
Install/Flash TWRP Recovery in your phone.
Download these files.
1 - modem.img ,
fsg.img
hw.img
2 - paste it into the adb folder and Open cmd/PowerShell here.
3 - Boot your phone into TWRP and execute the following codes in the cmd.
(Run the code containing hw.img at last. It doesn't matter if it executed first but that code will restart your phone while other two codes won't.)
Code:
adb push modem.img /dev/block/mmcblk0p1
adb push fsg.img /dev/block/mmcblk0p16
adb push hw.img /dev/block/mmcblk0p43
4 - After this, your phone will reboot and you can see two sim slots but it won't work as your baseband version will be "unknown".
Don't worry, the good news is that you got 2 IMEI back till here.
5 - Get the latest Firmware from XDA and reflash it. (See that you take the latest one.)
Your baseband version will change to its original.
6 - Dance like a Pro and hit Thanks to me..!
NOTE: - I tested it in MOTOROLA G4 PLUS - XT1643 - INDIA... I don't know other devices but can be tried rather than using the device like an iPod.
Click to expand...
Click to collapse
Phone is not rebooted after 100% is done.The command window got struck.help plzz what to doo?
hw.img got struck in xt1643
bonnyshroff said:
My Phone Story.
I flashed custom ROM.
Later Flashed back to stock ROM but I mistakenly flashed to old STOCK ROM and updated the OTA UPDATE.
Phone bricked.
After unbricking phone, its baseband version changed and overall it became to Moto G4 only with no FP sensor working and 2nd IMEI lost. Baseband version was also changed to something else.
After reading a lot of threads on XDA, I found a solution which many people ain't gave. (maybe out of their mind.)
I was suggested to flash hw.img. But it didn't help.
Later a link is given to me by XDA member thanx @echo92 and @Tengakallan. But his info was less.
Later I found the solution by that link.
The following things I did is mention below.
FLASH AT YOUR OWN RISK
'---------------------------- PROCESS STARTS FROM HERE---------------------------------------
Hoping you have adb fastboot and latest firmware on your pc.
Install/Flash TWRP Recovery in your phone.
Download these files.
1 - modem.img ,
fsg.img
hw.img
2 - paste it into the adb folder and Open cmd/PowerShell here.
3 - Boot your phone into TWRP and execute the following codes in the cmd.
(Run the code containing hw.img at last. It doesn't matter if it executed first but that code will restart your phone while other two codes won't.)
Code:
adb push modem.img /dev/block/mmcblk0p1
adb push fsg.img /dev/block/mmcblk0p16
adb push hw.img /dev/block/mmcblk0p43
4 - After this, your phone will reboot and you can see two sim slots but it won't work as your baseband version will be "unknown".
Don't worry, the good news is that you got 2 IMEI back till here.
5 - Get the latest Firmware from XDA and reflash it. (See that you take the latest one.)
Your baseband version will change to its original.
6 - Dance like a Pro and hit Thanks to me..!
NOTE: - I tested it in MOTOROLA G4 PLUS - XT1643 - INDIA... I don't know other devices but can be tried rather than using the device like an iPod.
Click to expand...
Click to collapse
XT 1643 got struck on both phone and bootloader
Can you explain more? What you mean by word struck?
is it struck or stuck?
And please reply with ScreenShot.
Hw.img got struck
bonnyshroff said:
My Phone Story.
I flashed custom ROM.
Later Flashed back to stock ROM but I mistakenly flashed to old STOCK ROM and updated the OTA UPDATE.
Phone bricked.
After unbricking phone, its baseband version changed and overall it became to Moto G4 only with no FP sensor working and 2nd IMEI lost. Baseband version was also changed to something else.
After reading a lot of threads on XDA, I found a solution which many people ain't gave. (maybe out of their mind.)
I was suggested to flash hw.img. But it didn't help.
Later a link is given to me by XDA member thanx @echo92 and @Tengakallan. But his info was less.
Later I found the solution by that link.
The following things I did is mention below.
FLASH AT YOUR OWN RISK
'---------------------------- PROCESS STARTS FROM HERE---------------------------------------
Hoping you have adb fastboot and latest firmware on your pc.
Install/Flash TWRP Recovery in your phone.
Download these files.
1 - modem.img ,
fsg.img
hw.img
2 - paste it into the adb folder and Open cmd/PowerShell here.
3 - Boot your phone into TWRP and execute the following codes in the cmd.
(Run the code containing hw.img at last. It doesn't matter if it executed first but that code will restart your phone while other two codes won't.)
Code:
adb push modem.img /dev/block/mmcblk0p1
adb push fsg.img /dev/block/mmcblk0p16
adb push hw.img /dev/block/mmcblk0p43
4 - After this, your phone will reboot and you can see two sim slots but it won't work as your baseband version will be "unknown".
Don't worry, the good news is that you got 2 IMEI back till here.
5 - Get the latest Firmware from XDA and reflash it. (See that you take the latest one.)
Your baseband version will change to its original.
6 - Dance like a Pro and hit Thanks to me..!
NOTE: - I tested it in MOTOROLA G4 PLUS - XT1643 - INDIA... I don't know other devices but can be tried rather than using the device like an iPod.
Click to expand...
Click to collapse
The hw.img got struck .The cmd get struck when 100% and not rebooting phone.What to do plz help?
charuvilapauljohn said:
The hw.img got struck. The cmd get struck when 100% and not rebooting the phone. What to do plz help?
Click to expand...
Click to collapse
Do the process again, wait for sometime to complete the process. It might show 100% but may be working internally. (never happened to me.)
run command for hw.img in last.
The command will restart your phone automatically.
Give a max of 15 minutes to restart.
If the problem persists, I'll tag some of my colleagues here.
Ok...thankssss....i will try...as you said above...
The problem again occure
bonnyshroff said:
Do the process again, wait for sometime to complete the process. It might show 100% but may be working internally. (never happened to me.)
run command for hw.img in last.
The command will restart your phone automatically.
Give a max of 15 minutes to restart.
If the problem persists, I'll tag some of my colleagues here.
Click to expand...
Click to collapse
I had waited for 1 hr and more...but no use.....please help...
charuvilapauljohn said:
I had waited for 1 hr and more...but no use.....please help...
Click to expand...
Click to collapse
@echo92
charuvilapauljohn said:
I had waited for 1 hr and more...but no use.....please help...
Click to expand...
Click to collapse
That seems to be fairly common - flashing the hw partition is hit or miss and various members have reported that the hw.img flash hangs or does not work. Which hw.img are you trying to flash?
Instead of flashing the hw partition, you could try to repair the partition - this post mentions downloading the factory NPJ25.93-14 stock ROM, which includes the scripts for programming a device. In there, there's a script for programming utags (which the hw partition is for). I'd suggest giving that a try. https://forum.xda-developers.com/showpost.php?p=76786219&postcount=12
Hi,
I am new to this forum, so may have missed the obvious ..
I have a Samsung Galaxy J5 Pro (SM-J530Y) and am looking for a Lineage ROM for it. I have found one for other versions of the J5 Pro (specifically [ROM][UNOFFICIAL]LineageOS 15.1 [8.1][J530F/G/S][10/05/18] - I would add a link but for some reason my system no longer copy and pastes .. )
I have used TWRP and set up the phone, and tried to load the ROM listed above, but the install ends with the message:
"E3004: This package is for device: j5y17lte, j5y17letub; this device isj5y17ltedx.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/lineage-15.1-20180510-UNOFFICIAL-j5y17lte.zip'"
I read this as I have got the wrong ROM zip file to load onto this phone. Can someone confirm this?
Also, can someone point me at a ROM image that will work (or more than one if there are more than one ...)
Thanks,
Tony
TechnoCurious said:
Hi,
I am new to this forum, so may have missed the obvious ..
I have a Samsung Galaxy J5 Pro (SM-J530Y) and am looking for a Lineage ROM for it. I have found one for other versions of the J5 Pro (specifically [ROM][UNOFFICIAL]LineageOS 15.1 [8.1][J530F/G/S][10/05/18] - I would add a link but for some reason my system no longer copy and pastes .. )
I have used TWRP and set up the phone, and tried to load the ROM listed above, but the install ends with the message:
"E3004: This package is for device: j5y17lte, j5y17letub; this device isj5y17ltedx.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/lineage-15.1-20180510-UNOFFICIAL-j5y17lte.zip'"
I read this as I have got the wrong ROM zip file to load onto this phone. Can someone confirm this?
Also, can someone point me at a ROM image that will work (or more than one if there are more than one ...)
Thanks,
Tony
Click to expand...
Click to collapse
For 8.1 ROMs you need a newer TWRP version , take the latest one and I think you won't have this problem anymore
RaiZProduction said:
For 8.1 ROMs you need a newer TWRP version , take the latest one and I think you won't have this problem anymore
Click to expand...
Click to collapse
Hi,
Many thanks for the reply.
I downloaded TWRP a few days ago, at the same time as I downloaded the .zip image, hopefully it is recent enough. It is version 3.2.1-0.
Is this recent enough? If not, can you point me at he latest suitable version (I tried looking around but as I am not familiar with the various sites, it still is a bit daunting.)
Thanks,
Tony
TechnoCurious said:
Hi,
Many thanks for the reply.
I downloaded TWRP a few days ago, at the same time as I downloaded the .zip image, hopefully it is recent enough. It is version 3.2.1-0.
Is this recent enough? If not, can you point me at he latest suitable version (I tried looking around but as I am not familiar with the various sites, it still is a bit daunting.)
Thanks,
Tony
Click to expand...
Click to collapse
That's a recent enough version , good luck , I hope it will work :fingers-crossed:
RaiZProduction said:
That's a recent enough version , good luck , I hope it will work :fingers-crossed:
Click to expand...
Click to collapse
Hi,
Sorry for the confusion - that is the version of TWRP that I used and it gave me those error messages.
From your reply then, it looks like the TWRP version is not the issue.
Can you suggest anything else?
Thanks,
Tony
TechnoCurious said:
Hi,
Sorry for the confusion - that is the version of TWRP that I used and it gave me those error messages.
From your reply then, it looks like the TWRP version is not the issue.
Can you suggest anything else?
Thanks,
Tony
Click to expand...
Click to collapse
Ok , it look like your device isn't the right one , because the codename verification revealed that the ROM you've flashed isn't for your device's variant.
I don't know why I didn't think about it earlier, but now you have the right answer .
If you want to flash something , you have to know what's your phone's codename , now you know it's "j5y17ltedx".
Try to find the zip file for your variant.
And also press the thank button if I helped you
Download Device ID from the Google Play Store then it should reveal the code name of your device. It should be the same as TWRP shows. You should only flash ROMs that matches the device codename on the device.
The application lists out your registered email account on this device, the device codename, and your Google Services Framework ID. The one you should be looking for is Device Codename.
HippoInWindow said:
Download Device ID from the Google Play Store then it should reveal the code name of your device. It should be the same as TWRP shows. You should only flash ROMs that matches the device codename on the device.
The application lists out your registered email account on this device, the device codename, and your Google Services Framework ID. The one you should be looking for is Device Codename.
Click to expand...
Click to collapse
Hi,
Thanks fro looking at this.
From the error message I get, I assume that the devicename is: sj5y17ltedx
Is this correct?
Note that I have got rid of the default Samsung operating system so cannnot boot it anymore (Since I had a ROM I thought would work I decided to bite the bullet and go for it. I may have been a bit hasty ...)
I have tried to search for that name (sj5y17ltedx) but there are no hits in this website (xdadevelopers). Does that mean no one has built a ROM for my version of phone yet?
Thanks,
Tony.
There are currently no ROMs that supported your variant instead of the stock deodexed version of the Stock ROM.
https://forum.xda-developers.com/ga...r-development/breeze-os-j5y17lte-7-0-t3732878
HippoInWindow said:
There are currently no ROMs that supported your variant instead of the stock deodexed version of the Stock ROM.
https://forum.xda-developers.com/ga...r-development/breeze-os-j5y17lte-7-0-t3732878
Click to expand...
Click to collapse
Hi,
OK - thanks for that. I have downloaded and installed the Breeze+ ROM you pointed to.
It looks like it is running OK. I will see how it goes over the next few days.
Many thanks,
Tony
TechnoCurious said:
Hi,
OK - thanks for that. I have downloaded and installed the Breeze+ ROM you pointed to.
It looks like it is running OK. I will see how it goes over the next few days.
Many thanks,
Tony
Click to expand...
Click to collapse
Hi Tony
Looking in to this device for lineage os and found this post
was wondering if this was a good substitute and if you had any feedback regarding the ROM after a few months (potentially) of use?
Cheers mate
Greetings my tech peoples.
Just wanted to let everybody know I successfully flashed a BNTV450 Stock Rom on a BNTV460 Tablet. As I said in a previous post, I bricked the little guy trying to get root (it got stuck in a bootloop after I patched Magisk to the boot-sign img and then flashed it) so I thought, why not be creative and see what you can do with the little guy.
Now there are problems. A **** ton of problems. It isn't what I would call functional. Screen keeps going Red on the borders and flickering. Start thing crashed. But I can get in and finagle to developer options and such. Flashboot and ADB still working though. Keep in mind I flashed with SP Tool via scatter file.
But hey - it can be done!!!!
Also, just for note, I've also been able to flash a boot img of the 450 over an installation of the 460 stock rom - did that unlocking the device. Honestly, that caused less problems but I wasn't able to get root. Also, it naturally erased my unlocking but fret not, I've unlocked the thing 3 times in the 12 hours I've had it.
This is my first nook device, and my first timed dealing with new android, Oreo. But I just wanted to give the hope out there.
Hopefully better news in the coming days.
You wouldn't want to share your scatter file and your stock firmware would you? Trying to recover a 450 that won't boot past Nook screen. I cannot unlock it because the volume key does not respond. I have been able to flash 1.02, 2.04, and 2.05 boot and recovery images from ipdev's thread with no change. Also got a 1.02 system.img from him but that did not seem to fix it either. I do not have adb access at this moment either so cannot logcat.
toasterboy1 said:
You wouldn't want to share your scatter file and your stock firmware would you? Trying to recover a 450 that won't boot past Nook screen. I cannot unlock it because the volume key does not respond. I have been able to flash 1.02, 2.04, and 2.05 boot and recovery images from ipdev's thread with no change. Also got a 1.02 system.img from him but that did not seem to fix it either. I do not have adb access at this moment either so cannot logcat.
Click to expand...
Click to collapse
This is the 450 firmware I used:https://mega.nz/#!Ds5lTCRD!MT8za1cUYOfEkSXGZB57gIsWr12ogWs9YotDoHZLwQ4
Scatterfile is in there. Keep in mind I got it from an unverified source - use at your own risk just in case it has that piece of software in the OS that B&N knew about which you can read about here: https://techcrunch.com/2016/12/22/the-new-barnesnoble-nooks-come-with-free-malware/
Articul8Madness said:
This is the 450 firmware I used: blob:https://mega.nz/f22bf6cb-5617-4e8d-9bea-5126793db71d
Scatterfile is in there. Keep in mind I got it from an unverified source - use at your own risk just in case it has that piece of software in the OS that B&N knew about which you can read about here: https://techcrunch.com/2016/12/22/the-new-barnesnoble-nooks-come-with-free-malware/
Click to expand...
Click to collapse
The link just defaults to the mega home page for me. Am I missing something?
toasterboy1 said:
The link just defaults to the mega home page for me. Am I missing something?
Click to expand...
Click to collapse
Sorry bro, it kept redirecting weirdly. I reposted the link in the previous post and it should work.
Here is also the site I got it from: https://www.xsfirmware.com/nook-bntv450-mt8163-android-6-0-firmware-flash-files/
Back up and running. Thank you.
toasterboy1 said:
Back up and running. Thank you.
Click to expand...
Click to collapse
No prob dude.
If spflash tool is working, but you have not a correct scatter file. You can use "Wwr_MTK tool" to read back the whole emmc and read partition table from preloader, the tool will make scatter file and full image copies of the firmware partition by partition
I did this, but now I can't log into the B&N account, and if I try to open nook settings, it asks me to log in, and again, it doesn't let me...