[Q] Problem flashing PA 3.6 - Sprint Samsung Galaxy S III

I just updated my TWRP to the latest version of 2.5.0.0; I then tried to flash the Paranoid Android 3.6 rom and I get "asset failed: getprop(ro.bootloader")
I've been flashing roms for the past two years and have never received this error before....
Any ideas on what this is or how to fix this?
Thank you

There's 20 posts regarding this issue. It's your bootloader that needs to be updated to the newest MD4 bootloader. Here is a link to latest md4 firmware aio update http://db.tt/Qt6NcH0a just flash this in recovery boot up and go back into recovery and flash the rom.
Sent from the future via Tapatalk 4

Related

Sgh-i747 4.4.2

Hello all. I just received a galaxy s3 from my sister in law running 4.4.2. I am aware I can't downgrade the complete firmware using Odin. The phone it's rooted. My question is what can I do with this thing as far as playing with roms and what not? Can I only install 4.4.2 based roms? Can I even unroot? I have been rooting and installing roms for years now but never have a phone felt more unfriendly before this. Thanks in advance.
Is the phone running stock 4.4.2?
You can install a custom recovery to the phone, copy some custom ROMs to an external SD card, and try out a bunch of ROMs.
Yeah its stock 4.4.2 rooted with clockwork mod recovery. Do the roms have to be 4.4 or 4.4.2 based? Tried cyanogenmod 4.3 and failed. I pretty much would like to flash via odin to go back to stock unrooted but 4.4.2 was over the air. Got 4.3 via sammobile but that fails. Kies won't show my device for firmware recovery. Shows it as normal to sync.
What error did you get when trying to flash CM10.2? Is your CWM up to date?
I would have assumed that CM10.2 would be comaptible with your KK bootloader and modem.
Do not make anymore attempts to flash 4.3 via Odin. This could result in a bricked phone because a KK modem on a 4.3 bootloader cannot be fixed using any method available on XDA.
Yeah I'm aware of the boot loader and modem downgrade issue. Tried odin once and just left it as is.
Is your CWM up to date? What error did you get when trying to flash CM10.2?
I don't remember the error. According to Rom manager, my recovery is up to date
What version is the cwm? I prefer to manually flash a custom recovery instead of relying on ROM manager.
Cwm 6.0.4.7. I've always used rom manager except for my galaxy nexus. Flashed with windows terminal and fastboot.
Since CWM is up to date, try flashing the most recent CM11.
Older cm roms, and any older roms should run fine on NE4. Some may not flash though, such as cm10. This is because the updater script doesn't include NE4 as it wasn't out when the rom was built. If you edit the script to make it flash, any of the available roms should run just fine.
As it stands though, the easiest thing would be to do as audit13 suggested and flash cm11. That and most other recent roms should flash just fine w/o any extra work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
well, after downloading the most recent cm11 nightly and gapps, rebooted into recovery and wiped. when trying to flash cm11, sd card not mounting. couldn't mount, restored a backup only to be greeted to a display that would not go to sleep and a fury of app and processes stopping pop ups. settings-accounts-backup and reset-factory data reset-etc did nothing but ask for a password. did it through recovery to a perfectly working phone with baseband version: unknown, IMEI: unknown, IMEISV: unknown. flashed the NE4 modem Doc posted in another forum, no dice. same message from cm as before. this time i remember. it was a bunch of basebands not including NE4.
And getprop ro.bootloader says NE4. first said unknown but maybe i typed it wrong.
Got it all back running. tried the S3Rx NE4 aroma zip that would end with installation aborted. found enewman17's post on updating using a stock-rooted 4.4.2 zip after flashing Doc's modem zip. all is well! So thank you DocHoliday77, and thank you enewman17!
Glad you got it working!
Sent from my SAMSUNG-SGH-I747 using Tapatalk

How to flash roms not based off 4.1.2 JB?

Hi, I'm having issues flashing roms which aren't based off of 4.1.2 firmware. I am rooted on 4.1.2 JB and have flashed a few of the 4.1.2 roms on my tmobile s3 t999, when I attempt anything else it fails with "error 7" for example cm10 and 11 or 4.3/4.4. Please Help? Thanks.
1. Make sure you're on latest version of recovery.
2. You may need to ODIN to a newer version/bootloader.
ShernDog said:
1. Make sure you're on latest version of recovery.
2. You may need to ODIN to a newer version/bootloader.
Click to expand...
Click to collapse
I tried flashing over the bootloader update found here. http://forum.xda-developers.com/showthread.php?t=2282603
and am receiving a "status 7" error once again. I restored a backup which contained no mods, downloaded rootkeeper and booted into cwm tried flashing the updated zip, it returned a status 7 error. I'm not sure how to proceed. I am currently using 4.1.2 axis with trinity kernel. I cant seem to flash anything whatsoever aside from roms based off 4.1.2. Can someone help me step-by-step?
thanks
Update recovery
thanks guys. Success!!!

installing revolution HD w/ twrp?

hi guys - so i tried to install the revolution rom on my recently unlocked m9 and it'd only boot to the bootloader or download.
i found some threads back from 2012 that said twrp wouldn't install the rev rom, but suspect it's out of date - it seemed to work fine.
is there some magic here? i tried to flash my firmware to the version matching the rom (3.35.401.12) and got a code 10 failure in adb. my current firmware is 3.10.605.7. doesn't flashing the rom update the firmware too? or do i need to successfully flash the rom prior?
should i use a different recovery? twrp launched the rev aroma installer and all seemed to go perfectly smoothly... no problems came up until reboot brought me right back to bootloader.
the aroma install says it might boot loop a couple times, but i booted to bootloader 5+ times before giving up and going back to a deodexed stock vzw rom.
any help is greatly appreciated - i'm hoping to get up to marshmallow before calling it good enough and moving on.
Flashing the rom doesnt update the firmware. S-on makes sure of that.
You must be on the base firmware for the rom to take. You need the vzw marshmallow ota update before you can flash a marshmallow based rom.
Sent from my HTC One M9 using Tapatalk

CM update won't install

I'm trying to install the latest update to cm13 but it errors out. I'm only running stock CM with no custom kernel. I've also tried a full wipe and reinstall but get the same error message. Any help is appreciated.
Which rom are you running now? If it's lollipop based then you need to flash marshmallow to then flash cm13 over the top of it.
If you are s-on you have to use an ruu or an ota. If you are s-off there are plenty of zips around you can flash.
The principle is, you need a base rom to flash the "incomplete" cm13.
Sent from my HTC One M9 using Tapatalk
You need to update your firmware to the latest version and then you will be able to flash the new ROM.

Unable to update to new versions of TWRP & ViperOne Rom

Hi All,
Iv'e never posted here before, but I'm having issues updating to a newer version of TWRP and updating to the latest version of the ViperOne Rom.
I am currently using TWRP v2.8.7.0. I attempted to flash the latest version 3.0.2.0, but the recovery fails to load once I have flashed it. If i flash back to the older version the recovery works straight away.
The reason I am trying to install the newest TWRP is because newer ViperOne Roms don't seem to work when flashed. I am currently using ViperOneM9 V3.5.0. None of the later versions are working for me. Once I flash the newer Roms, the handset keeps booting back to the bootloader.
Does anyone have any idea why these problems are happening? I have no idea what to try next.
Thanks
JM92W said:
Hi All,
Iv'e never posted here before, but I'm having issues updating to a newer version of TWRP and updating to the latest version of the ViperOne Rom.
I am currently using TWRP v2.8.7.0. I attempted to flash the latest version 3.0.2.0, but the recovery fails to load once I have flashed it. If i flash back to the older version the recovery works straight away.
The reason I am trying to install the newest TWRP is because newer ViperOne Roms don't seem to work when flashed. I am currently using ViperOneM9 V3.5.0. None of the later versions are working for me. Once I flash the newer Roms, the handset keeps booting back to the bootloader.
Does anyone have any idea why these problems are happening? I have no idea what to try next.
Thanks
Click to expand...
Click to collapse
In one word, u must upgrade to a Marshmallow firmware, because latest versions are compatible only with Marshmallow (Android 6).
This is a good place to start reading:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Fain11 said:
In one word, u must upgrade to a Marshmallow firmware, because latest versions are compatible only with Marshmallow (Android 6).
This is a good place to start reading:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
Thanks so much. I appreciate your help.

Categories

Resources