Related
Hi guys.
My phone has been having major signal issues, no signal or emergency calls only next to an exact same phone that has no problem. Talking to my provider, it appears to be the phone and I need to send it back for repair. Problem is, I have a different firmware on there. I obviously need to get it back to the stock optus rom it came with. I know computers and stuff, but im a bit lost in this area. I've done a lot of searching on here but can't seem to find a specific resolve to this issue.
I'll try and sum it up.
Currently running Litening Rom 5, which i flashed with odin. I found on here the link for the original optus branded rom (GT-I9100_OPS_I9100XWKE7_I9100XXKE4_I9100OPSKE4) but after downloading it I'm more lost. The 7zip file had the following files in it:
boot.bin, cache.img, factoryfs.img, hidden.img, modem.bin, param.lfs, sbl.bin and zimage.
I have no idea what to do with these. I've also read that CWM is another possible way to do all this. My rom has it so that might be possible. I'm not fussed about keeping any files, I was gonna do a factory reset before I send it away anyway. I wanna completely wipe my phone and get it back to exactly how it was, so when optus look at it, its how they sent it to me, especially with no yellow triangle on boot.
What should I do with these files? The other option I have is if I can get the rom dumped off a friends optus phone and simply put it onto mine. I know 2 friends with them, can I plug their phone into my PC and use the dump button in odin, or will I get the same files?
Other question I have are:
1) Will Optus know what version of the firmware came on the phone (XXKE7 or whatever) and therefore realise a possible older version is on there, causing suspicion?
2) Is it possible that custom firmwares can screw up my reception? Friends are running stock and they have no issue, though saying that, its still not as good signal as a Nokia.
If you've read this far, thank you very much, I really appreciate it. I'm just so lost, freaking out a bit, going a bit insane with the phone constantly not having signal and just low on time to sort it out. Any help would be appreciated. Thank you!
Hi.
First off, if you're already down to the .bin and .img files, you extracted too much.
The archive you downloaded should contain a .tar file - DO NOT extract this one! You need the .tar as .tar.
Then download an App called "Odin" (likely to be found in the very same thread where you found the firmware) and use that one to flash the .tar onto the phone.
Instructions for that are also in the thread where you found the firmware.
That should already solve most of your hazzle.
If I'm not mistaken, flashing your phone's kernel would case
Cause the binary flash counter to clock. And the phone does keep a record of how many custom kernels you have been through. So I would say if they wanted to know, they would be able to find out.
In that case, spend the 5 to 10 bucks on eBay for the USB jig that resets the counter.
I have one too, "works nicely" is an understatement
HellcatDroid:
The one file I downloaded was a 7zip compressed exe. When I extracted that, I got the listed files, there was never a .tar file.
I had no idea about the kernel flash counter, but it sounds like it could be an issue. I saw those USB jigs, but though they were just a way to get into downloading mode if you'd somehow screwed up the normal way. Is that all they do, or much more?
TroyX87 said:
HellcatDroid:
The one file I downloaded was a 7zip compressed exe. When I extracted that, I got the listed files, there was never a .tar file.
Click to expand...
Click to collapse
You're doing it wrong.
Intratech said:
You're doing it wrong.
Click to expand...
Click to collapse
You know what would be awesome? If you explained why. I have no idea why I'm doing it wrong. Did I download the wrong file? (didn't have many options). Or would it be better to get a dump from a friends phone that has the desired rom/kernel?
How do I know why you're doing it wrong? The files are self extracting, all you need to do is double click it and point to when you want the included tarball extracted. You will then have a single tarball which includes everything in a single package. This has all been covered in the tutorial.
The file was a compressed exe, I dont think loading it on as a rom would have worked. Though when I extracted that (self extracting exe), I ended up with all the seperate files, there was never a .tar.
Is it safe to simply put those files into a .tar file with winrar? Is that all it is? Or will I risk bricking my phone? I had a look in the tutorials but couldn't see anything about it.
Thanks
TroyX87 said:
The file was a compressed exe, I dont think loading it on as a rom would have worked. Though when I extracted that (self extracting exe), I ended up with all the seperate files, there was never a .tar.
Is it safe to simply put those files into a .tar file with winrar? Is that all it is? Or will I risk bricking my phone? I had a look in the tutorials but couldn't see anything about it.
Thanks
Click to expand...
Click to collapse
Where did you get the file from? Optus firmwares are in the carrier branded firmware thread in the dev forum so you can download a copy from there.
I grabbed the exe from your other thread, it had 5 different links and only 1 worked at the time.
But you know the worst part? I just figured it out. The exe extracted a .tar file, but in my rushing and stressed-ness, i didn't realise that was the one, it was a winrar file so i just thought it was compressed or something, like a zip.
My bad. I wont be flashing just yet, gonna replace my sim card first. I got used to the idea of wiping my phone and starting again, but now I realised how annoying that would be. Bought a USB jig too, just in case.
Appreciate your help, sorrying for being a n00b!
After searching around in the forum, I have a specific question I cannot find the answer to.
I am presently on the overcome 2.2.0 Rom (P7510, XWKL1). The result of this is that, of course, it cannot be updated through KIES.
My Kies downloaded a file for upgrading my 7510, which can be found on the harddisk, and is XWKL1 stock for my Dutch region (PHN). The Overcome Rom is XAB.
In preparation for ICS (stock, coming in the next two months I hope), I would like to go back to the stock XWKL1 for PHN.
I am stuck as to the procedure though:
1) restocking with the overcome restocking will not be PHN as well, so Kies will not upgrade for PHN
2) I have found the firmware upgrade file on my harddisk, but is has no extension and therefor I do not know how to install this over overcome 2.2.0. How do I turn this file into something I can flash?
Who can give me the precise instructions here?
Hi I'm also looking for a long time to a Dutch ROM PHN csc
You'll have to use Odin and a stock firmware from samfirmware.com
You also have the flashing guide on the same site
I installed the ROM via odin but in none of the stock ROMs is the Dutch csc present.
** Bumping this **
As I have note been able to sort out what I wanted, I'll try again with this bump.
Specifically tryin to find the answer to question 2 in my OP:
2) I have found the firmware upgrade file on my harddisk, but is has no extension and therefor I do not know how to install this over overcome 2.2.0. How do I turn this file into something I can flash?
Have searched again in the forums but did not find the answer.
All files have some sort of extension. At least in my experience. It may not show but it's still got a file type/extension. On a windows machine find the file and right click on it and choose properties. It should show xxxxx.yyy where yyy is the file type/extension. Post what it is and someone will let you know what to use it with.
This is my best suggestion.
Sent from my GT-P7510 using one stinky finger.
The file really has no extension. I have showing the extensions turned on in windows, so it would show if it had one. The filename is: XWKL1PHNKK1XWKL1XWKL1 and giving it a .zip or .rar extension does not make it readable.
I'm at a loss then. I've never seen a file that didn't end with (dot)something. I'll look more into it and hopefully someone will help before it's lost.
Sorry I couldn't help.
If you see this it was sent using my GT-P7510.
When kies downloads a firmware it saves it in a file that only Kies can read, I would however suggest you just get it downloaded from sammobile site, as they have it there, you may need to register, but I do hope their file sharing issues are rectified and the links still work... Bloody SOPA.
You could however factory reset?
I could, but Sammobile does not have this firmware/CSC combination available for download. Do you know of someway to kickstart Kies into installing the firmware it has downloaded, so I can go back to a restoch and then force the install of this firmware?
Doodle said:
I could, but Sammobile does not have this firmware/CSC combination available for download. Do you know of someway to kickstart Kies into installing the firmware it has downloaded, so I can go back to a restoch and then force the install of this firmware?
Click to expand...
Click to collapse
Well like I said, back then the original firmware files would consist of 3 different files, the Phone/PDA/CSC, you just need the PDA file, Apparently they've made it easier now by making sure all you need is the PDA file and just to flash that file via Odin in the *not so obvious * PDA slot, It now contains the CSC/Regional of the desired firmware and the modem.img
Misledz said:
When kies downloads a firmware it saves it in a file that only Kies can read
Click to expand...
Click to collapse
Just a quick question, what is a Kies file format? Is it xxxx.yyy or just xxxx with yyy being a format or extention?
Or am I just completely ignorant on this?
If you can read this it was sent using my GT-P7510.
Benzoman said:
Just a quick question, what is a Kies file format? Is it xxxx.yyy or just xxxx with yyy being a format or extention?
Or am I just completely ignorant on this?
If you can read this it was sent using my GT-P7510.
Click to expand...
Click to collapse
As far as I know the format is somewhat like xxxyyy it's just a dump file, I haven't gotten around to waste time and figure what app works best on opening/converting, and plus it's risky since if the normalboot.img doesn't get flashed you may end up with a brick but I'm pretty sure its in a md5 format or a tar atleast.
Hi guys n girls,
I am sort of new to the Ace section here. I am doing a re-vamp of my mum's phone and said I would spruce it up a little. Shame there is no decent CM 9 versions that I can get working because of lack of RAM....the only one listed (no disrespect to the dev - thanks for making it available on such a low spec device!) but it doesn't work with my Optus GT S5830V (5830I) for some reason?
Anyway to my point, I have downloaded several versions of the stock firmware from Sammobile. The odd thing is that I cannot extract that firmware at all. Every archive program I have sees it as either being not an archive; corrupt or fails to extract it? So I am unable to make my own 4 part Odin recovery package. Making my own will save time; at the moment I have to flash the 4 part Odin (return to stock) package, then reboot into download mode again and then flash the stock firmware?
3 things I noted.
1). The device is not detected by the so called Odin specific for Ace and variants that uses an Ops type PIT file? The device is plugged in and all drivers upto date....it' just plain doesn't see it? It is however detected and flashable (albeit without an .ops file) using the 4 part package on Odin 3.07 made for my Galaxy S3?
2). I am unable to get any detection with EFS pro and it returns no PIT file?
3). All attempts to extract the stock Optus firmware package fail. I have removed the .MD5 file extension (only needed for preserving file naming conventions anyway - i.e. If you rename any .tar.md5 firmware package, in order to be able to flash it you need only to remove the .md5 from the end and leaving it as .tar and the firmware will flash without error. I digress.....What does someone suggest for me to being able to make my own firmware package based on stock?
First off, wrong section.
Jarmezrocks said:
Shame there is no decent CM 9 versions that I can get working because of lack of RAM....the only one listed (no disrespect to the dev - thanks for making it available on such a low spec device!) but it doesn't work with my Optus GT S5830V (5830I) for some reason?
Click to expand...
Click to collapse
1) We don't have a stable CM9 because our devs don't have the source code for all the drivers, not lack of RAM.
2) Have you formatted your system's partitions to the EXT4 filesystem? CM requires an EXT4 filesystem to operate.
Jarmezrocks said:
Anyway to my point, I have downloaded several versions of the stock firmware from Sammobile. The odd thing is that I cannot extract that firmware at all. Every archive program I have sees it as either being not an archive; corrupt or fails to extract it? So I am unable to make my own 4 part Odin recovery package. Making my own will save time; at the moment I have to flash the 4 part Odin (return to stock) package, then reboot into download mode again and then flash the stock firmware?
Click to expand...
Click to collapse
Jarmezrocks said:
3). All attempts to extract the stock Optus firmware package fail. I have removed the .MD5 file extension (only needed for preserving file naming conventions anyway - i.e. If you rename any .tar.md5 firmware package, in order to be able to flash it you need only to remove the .md5 from the end and leaving it as .tar and the firmware will flash without error. I digress.....What does someone suggest for me to being able to make my own firmware package based on stock?
Click to expand...
Click to collapse
The tar.md5 file has to split into the PDA, CSC, Modem and PIT files using Odinatrix. Search for it.
Jarmezrocks said:
3 things I noted.
1). The device is not detected by the so called Odin specific for Ace and variants that uses an Ops type PIT file? The device is plugged in and all drivers upto date....it' just plain doesn't see it? It is however detected and flashable (albeit without an .ops file) using the 4 part package on Odin 3.07 made for my Galaxy S3?
Click to expand...
Click to collapse
The Odin specific for Ace you stated above might be for GT-S5830. For the variants running the Broadcom BCM21553 the Odin version to use is v1.84. Odin v3.07 is more like a universal Odin that works on most devices.
Jarmezrocks said:
2). I am unable to get any detection with EFS pro and it returns no PIT file?
Click to expand...
Click to collapse
I don't know about this.
NightRaven49 said:
First off, wrong section.
Click to expand...
Click to collapse
Why? I was not actually asking for support as such, just sharing what I learnt/noticed.
NightRaven49 said:
1) We don't have a stable CM9 because our devs don't have the source code for all the drivers, not lack of RAM.
2) Have you formatted your system's partitions to the EXT4 filesystem? CM requires an EXT4 filesystem to operate.
Click to expand...
Click to collapse
Yes I am aware of that. I actually did attempt to flash the CM9 developer package several times all without result.
I tried many methods, firstly the conventional method and then several other unconventional methods. I first flashed CWM recovery 6.0.0.x (something around there) and that was ok but it could not detect the partitions....naturally I was on the standard firmware!
So I then flashed Thunder kernel which allowed recovery to see and mount all the partitions as well as prepare for a CM firmware flash. As I knew that CM required EXT4 I was prepared and flashed Rio's Ext4-RFS conversion script via Aroma in recovery. This worked very well. Only issue was that in doing so it corrupts the system partition and then I am unable to mount it anymore to flash CM.
Returning to stock or even attempting a nandroid restore from this point forward was fruitless as you can imagine. I tried several other combinations before retiring the idea. These included full system wipe after flashing CWM recovery (I figured maybe having data on the partitions its self could be interferring with the EXT conversion scripts? Everything seemed fine and ran correctly as expected only no system mounting.
I tried another method of flashing a ROM that included a kernel with it based on CM7 in the hopes that migrating to CM9 would be easier; this was not the case.
I picked a CM7 ROM that had a conversion script built in for BML to MTD. After returning to stock base via Odin I proceeded to flash recovery 6.0.0.x again, then I immediately flashed CM7 in the hope that I would kill two birds with 1 stone and have CM do its conversion on the fly as well as install (alleviating the need for mounting system after migrating to Ext4). This ROM installed without fault. All was well until I rebooted expecting to boot into CM7....this wasn't the case, I received bootloops like crazy. Naturally I booted into recovery (the ROM had downgraded me to version 5.x CWM recovery - that is fine anyway); I proceeded by clearing the caches and performing a factory reset (note This usually a good thing to do anyway regardless if you came from a clean reset factory firmware or not).
After doing this and rebooting the device reboots continuously as it did prior. I again decided to re-install the same zip as I am aware with changing to CM on many other devices it can sometimes require flashing 2-3 (and sometimes even 4) times for a firmware update to stick. Again still no response and forever bootloops. I decided at this point that if I was to waste the time and effort in Odin'ing back to stock AND THEN flashing my standard firmware that I should try another CM ROM.
I had CM9 available and even though half hour prior I was unable to mount the the system partition, I thought maybe that CM7 had been flashed first so if CM9 can see and mount partitions (like it should have originally) then I could flash CM9 in a hope that it might wipe out what ever was causing all the issues with bootloops.
CM9 installed correctly, however again I could not boot the device at all! I had read a post from a forum member's guide saying that if I got some of these issues that I should flash back to base and try it again. I did this another 3-4,5 times at least, various combinations of wiping base firmware, not wiping base firmware, wiping CM7; not wiping CM7......Always the end result = bootloops.
As you can imagine it was rather annoying if I was returning to base firmware (if I wanted to be stock carrier branded again I needed to flash twice, once to return to stock and again to flash Optus firmware.
Overall I was unable to get any firmware booting besides that which was provided as an Odin package AKA stock firmware. If I flashed a custom recovery over stock firmware I was unable to boot again. Oddly enough I found a standalone version of CWM recovery version 5 that was not CM specific and I performed a backup as it was able to see the stock partitions without throwing errors.
I then opted to do a conversion to EXT4 again and hoped that I could just restore my nandroid backup of the stock partitions like recommended in may of the guides for Galaxy Ace.
Unfortunately again I was unable to boot and the partitions become unmountable leading to yet again flashing back to base unbranded, then flashing stock carrier branded firmware (this has the correct modem for the carrier and region).
At this point I retired the idea of custom firmware. I will later root the device and just leave it on 2.3.7 and do internal/external SDcard swap and flash a theme and maybe a few compatible APKs from newer stock firmwares (at least ICS) to achieve the functionality I was hoping to have by flashing and using ICS. I found the best and most simplest way of achieving this was through Moto-Chopper Root method and adb, most of the documented ways of achieving root on the Ace don't work for the S5830V for some reason. So I will stick with what works.
NightRaven49 said:
The tar.md5 file has to split into the PDA, CSC, Modem and PIT files using Odinatrix. Search for it.
Click to expand...
Click to collapse
Thanks for the tip. :good: I have downloaded this ready now, so I will investigate how this goes? It looks very similar to a application I already use TAR.MD5_PACKAGER however I see it has an option for extracting from .tar.md5 files that have malformed header information. So that sounds like it should do the trick!:fingers-crossed: Do you think that this is maybe intensional as a means of stopping people like us from building custom firmware packages?
I mean the .tar.md5 package flashes perfectly as it should do which is very surprising seeming .md5 signature is very easily broken when you rename the file and you have not even opened it. That was what lead me to flashing it in the first place, I mean I figured that if the .tar.md5 was so corrupt as I believed it was, then the worst that can happen will be Odin will spit an error message and not proceed i.e. it won't even attempt to flash the said firmware!
Myself if I download any firmware that doesn't flash and fails due to md5 error, I immediately open it up and inspect it and unless it was extremely difficult to obtain (I have waited close to 30 hours once for an old firmware package to download from the only source I could find - but regardless if it was damaged or not I only wanted the old bootloader so I could integrate it into a new firmware package so the passing md5 was relatively unimportant), I would just re-download it again.
The fact that ALL of these packages for S5830I are like this (regardless of what browser or means I downloaded the package) and the fact that they DO in fact flash like normal packages, and the phone returns to 100% factory condition; tells me that this does look like a means of discouraging custom firmware developers? hmmm
NightRaven49 said:
The Odin specific for Ace you stated above might be for GT-S5830. For the variants running the Broadcom BCM21553 the Odin version to use is v1.84. Odin v3.07 is more like a universal Odin that works on most devices.
Click to expand...
Click to collapse
The device is actually a S5830V...the V devices are relatively undocumented, but they are essentially just the same as the more common i/M variants. I did my homework first with this, and I can most certainly attest that it is NOT the S5830. I wouldn't attempt flashing S5830 firmware, also S5830i firmware boots and functions as normal and has signal albeit not so strong when the modem is not for our carrier and/or region, but function none the less.
NightRaven49 said:
I don't know about this.
Click to expand...
Click to collapse
Well give the fact that I had performed so many download of firmware that I initially believed to be corrupt I was unable to extract the PIT (or in the case of the generic Ace OPS file) from the firmwares.
Being the fact that there was little known about the S5830V I was unsure if to proceed of not? There are few reports on the device and most of them were of owners bricking their device, only 1 report I know of where a V owner claimed he flashed S5830i firmware without a hitch, again he was not from Australia where I am from, so I was flying blind and scared I was going to brick the device.
At the very least if I had a PIT file I could analyse it and could manually make image backup of the EFS/IMEI partition straight after rooting the phone. I have looked already at scripts that scan the whole emmc and I hit a snag when the kernel I am using is not insecure i.e. adb cannot run as root. I have root and confirmed with root checker app but terminal emulator and/or command line are unable to obtain root
Anyway to shed some light for you EFS Pro is a means of doing this that works on most Samsung devices....just not the Ace as far as I can tell.
Yes I am already aware that there is Galaxy Toolbox and I had actually gone ahead and done all that already,but an incident more recently where I had a device I was repairing with a wiped IMEI and it actually refused to boot. This becomes a hassle when restoring the IMEI cause in order to have Galaxy Toolbox you need to be booted and rooted. I wasted a whole day repairing the IMEI. So pretty much the message here is what good is Galaxy Toolbox to me restoring the IMEI if it can't boot? NONE!
I contacted the developer weeks ago and explained my situation and he is still yet to respond. I explained that I had a V variant of the Ace and wanted to ensure I had all bases covered. I requested information on how I could open the IMEI manually outside of the Galaxy Toolbox in the case that it would not boot (as this was how I restored the other device last week and it worked), unfortunately I am still yet to hear a response form him? Slack.
When I obtain this information I will share it here on XDA in the hopes that people in Australia with this variant will search and find some info on it. This is also why I am making this post here so detailed for folks like me who have been searching fruitlessly for answers.
My thoughts are that maybe there is something still not 100% the same between the i and the V because all custom firmwares I tried made for the S5830i never worked?
There is maybe an issue with how they are scripting their installs that is causing issues, but it is worrying enough that flashing so far has lead to partitions becoming corrupted very easily. I have had this before with my own phone more recently because a dev made a simple mistake in an updater script that called an explicit partition by mounting point ID and not by a more generic mounting point like "/system", "system" which lead to lost IMEI and bricked phone.
I am not blaming the dev though because it is easy to assume that a even though the mounting was non-specific for my device and the partition being called was not actually the EFS, it should not have corrupted my EFS....but that is not true, so a discovery was made and a lesson learned from all this. I managed to revive my device and it lived to fight another day, but simple mistakes made in ignorance or lack of information can still be costly mistakes. Need I say more.
I will report back when I have got a proper partition map for the S5830V and all will be happy days
I don't feel like quoting anymore, but I do spot some anomalies.
1) ...we don't have CWM 6.0.0.x. Are you sure you used the 5830i CWM, not the 5830?
2) I was referring to some other version of Odin when you said the Odin version specific to Ace. Which version were you using then?
3) I don't see how rio's multi-formatter can render the system partitions unmountable. In that case try lopicl.00's EXT4 formatter. Go search for it. After formatting flash Biel's Specific Basic kernel.
also you were asking a question, so naturally this should be in Q&A.
Hi,
after flashing ROM ,my phone reboots from Androids Start screen (with choose language). I try many times wipe from recovery and flash with other stock roms manually by fastboot.exe but phone still reboots at Android start screen. Its Android 2.3.5. Help
Gee81 said:
Hi,
after flashing ROM ,my phone reboots from Androids Start screen (with choose language). I try many times wipe from recovery and flash with other stock roms manually by fastboot.exe but phone still reboots at Android start screen. Its Android 2.3.5. Help
Click to expand...
Click to collapse
Need more details. Which carrier is the phone from? What rom did you try? Which recovery are you using? Which fastboot files did you try? Did you perform a factory reset after fastbooting the files?
But as a general rule for these types of Motorolas, if you get in a spot where nothing else is working, then using the proper sbf file and RSDLite should get it going again.
es0tericcha0s said:
Need more details. Which carrier is the phone from? What rom did you try? Which recovery are you using? Which fastboot files did you try? Did you perform a factory reset after fastbooting the files?
But as a general rule for these types of Motorolas, if you get in a spot where nothing else is working, then using the proper sbf file and RSDLite should get it going again.
Click to expand...
Click to collapse
I bought phone by ebay. Was brand new,and originally Rom was 5.5.1Q-110_ELWLA-TA-28_BellMobility_1FF , I was update by Rds Lite to little bit newest 5.5.1Q-110_ELWLA-TA-39_P025_A016_BellMobility_1FF.signed.xml.zip and it was all good. But I decide back to originally Rom. Again with Rds Lite I flashing the originally Rom but it was an fastboot error and it stop flashing. So I remove battery and again by Rds Lite flesh this new working well Rom. But now is reebotloop - when I turn on phone it load well only to Android's start scrreen then reboots in loop. I use stock recovery (holding rm when turning on phone) and factory reset.
fastboot files i used are moto-fastboot and also fastbot from Android SDK
After fastbooting I preformed factory reset.And after that is is still the same
Gee81 said:
I bought phone by ebay. Was brand new,and originally Rom was 5.5.1Q-110_ELWLA-TA-28_BellMobility_1FF , I was update by Rds Lite to little bit newest 5.5.1Q-110_ELWLA-TA-39_P025_A016_BellMobility_1FF.signed.xml.zip and it was all good. But I decide back to originally Rom. Again with Rds Lite I flashing the originally Rom but it was an fastboot error and it stop flashing. So I remove battery and again by Rds Lite flesh this new working well Rom. But now is reebotloop - when I turn on phone it load well only to Android's start scrreen then reboots in loop. I use stock recovery (holding rm when turning on phone) and factory reset.
fastboot files i used are moto-fastboot and also fastbot from Android SDK
After fastbooting I preformed factory reset.And after that is is still the same
Click to expand...
Click to collapse
So after you redid the newer update with RSDLite, it didn't work again? Seems odd... Did you get any error messages during the install? But some phones / updates support downgrading and some don't. Sounds like that's the main issue...
123
es0tericcha0s said:
So after you redid the newer update with RSDLite, it didn't work again? Seems odd... Did you get any error messages during the install? But some phones / updates support downgrading and some don't. Sounds like that's the main issue...
Click to expand...
Click to collapse
I tried different Roms from here fwteam.grupoandroid.com/PRO+%20MB632/ - i didnt find any other sourcre of mb632 roms. But RsdLite flash it to phone but always is the same story- phone reboot at Androids start screen. Or I also tried like i sad manually flash every file by fastboot.
You spoke about sbf files. Well I was looking for them few days ago. I didnt find any for Pro+ mb632, I found only for ProXT610. I found for Pro+ mb623 only this zipped Rom's contains of
PHP:
7x30_recovery_bl.mbn
adsp.mbn
boot.img
cdrom.img
dbl.mbn
emmcbld.mbn
emmcboot.mbn
fat.bin
motoinitlogo.img
MPRG7x30.hex
NV_RBU_plus_bp_flex_modem_bkp.bin
osbl.mbn
p3_elway_user_BellMobility_MB632_5.5.1Q-110_ELWLA-TA-39_P025_A016_1FF.signed.xml
partition.bin
recovery.img
svn.bin
system_part1.img
system_part2.img
I don't know are there any *.sbf files for Pro+ mb632 ? because I cant find any
Gee81 said:
I tried different Roms from here fwteam.grupoandroid.com/PRO+%20MB632/ - i didnt find any other sourcre of mb632 roms. But RsdLite flash it to phone but always is the same story- phone reboot at Androids start screen. Or I also tried like i sad manually flash every file by fastboot.
You spoke about sbf files. Well I was looking for them few days ago. I didnt find any for Pro+ mb632, I found only for ProXT610. I found for Pro+ mb623 only this zipped Rom's contains of
PHP:
7x30_recovery_bl.mbn
adsp.mbn
boot.img
cdrom.img
dbl.mbn
emmcbld.mbn
emmcboot.mbn
fat.bin
motoinitlogo.img
MPRG7x30.hex
NV_RBU_plus_bp_flex_modem_bkp.bin
osbl.mbn
p3_elway_user_BellMobility_MB632_5.5.1Q-110_ELWLA-TA-39_P025_A016_1FF.signed.xml
partition.bin
recovery.img
svn.bin
system_part1.img
system_part2.img
I don't know are there any *.sbf files for Pro+ mb632 ? because I cant find any
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1709959
A member on the 3rd page said this worked for him. I'm assuming he used the English one as I didn't see anything specifically say Bell.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=1709959
A member on the 3rd page said this worked for him. I'm assuming he used the English one as I didn't see anything specifically say Bell.
Click to expand...
Click to collapse
Thenks,those files I tried already before I ask for help on this forum. But fleshing these files didnt help at all. I read about to unbrick other Motorola's like ProXT610, to flash it with stand alone sbf files becouse these from Your link contains:
7x30_recovery_bl.mbn
AdbWinApi.dll
AdbWinUsbApi.dll
adsp.mbn
boot.img
cdrom.img
dbl.mbn
emmcbld.mbn
emmcboot.mbn
eprj-mfastboot.exe
fat.bin
FlashME.bat
motoinitlogo.img
MPRG7x30.hex
NV_RBU_plus_bp_flex_modem_bkp.bin
osbl.mbn
p3_elway_user_BellMobility_MB632_5.5.1Q-110_ELWLA-TA-39_P025_A016_1FF.signed.xml
partition.bin
recovery.img
svn.bin
system_part1.img
system_part2.img
I don't know is there any diference between stand alone sbf file and this file contains many files.I dont know is there even any stand alone sbf's files for Pro+. I hope You know what I mean becouse Polish is my native language.
Edtit
Today i found a new tip, to try clear the dalvik-cache and then flesh. I dont know how clear it without acces to Android, with no root and no custom recovery
Hello,
So a friend of mine gave me his j3 Achieve to get unlocked. It has the FRP lock activated so I'm wanting to clear it by reflashing the original stock firmware to the device. However, I'm only seeming to find firmwares that are the wrong version.
I'm looking for the PVPU4BSJ2 varient of the sm-j337P firmware, anyone have a link to that?
EDIT:
So i got to looking at the PIT file from the device, and it reports the firmware version as J337PVPU1ARG3, but yet the recovery still says J337PVPU4BSJ2. So i have a feeling i need to find the PVPU1ARG3 firmware, but its nowhere to be found on the net, unless i want to pay for a subscription to some bs firmware site.
So if anyone has this version of the J3's fimware please let me know and share. Otherwise I could use some help figuring out if im even right about the version. Ive included a link to the PIT file and pics of the recovery menu and the back of the device.
I'm using Heimdall v1.4.2 on Linux Mint 19. It will sucessfully flash all the firmware images except for the system image, it keeps erroring out saying it cant open the system.img file. I suspect the image is too big (idk why since its stock, maybe I just need to use ODIN)
PIT File and screens: https://drive.google.com/open?id=1VSVoLtHK5d-Sm3ja8hy_X4WJakJfvEgu
Any help is greatly appreciated, thank you in advance!
So I may have found the correct firmware. I found samsung-firmware.org and it seems that they have the correct version I need. However they throttle the download speeds heavily. So a trick I found is to use the commandline downloader Axel on Linux.
Using Axel gets me almost 500kbps downloads speeds instead of the 120kbps that Firefox gets.
Link included below. Make sure to get the correct region!
https://samsung-firmware.org/firmware/pda/J337PVPU4BSJ2/
EDIT:
So I've tried the firmware above and the device is still stuck in a boot loop, and i can't see to flash the system.img image. Heimdall keeps giving me an error saying it can't open the system.img file.
I also discovered that in my PIT file, it says the firmware version is J337PVPU1ARG3.
So I've tried looking for that version and I can't find it ANYWHERE.
Ain't gonna lie I'm stuck on this one, so any help is greatly appreciated.