yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Princess.:
Hi

I have a Samsung Galaxy core prime running on lollipop 5.1 and I recently rooted it with kingroot 6.1.

Everything has been fine ever since then. I've been getting notifications about some kind of update kingroot has but I ignored it cause I didn't think I needed to. Anyways I don't know if anything I just mentioned has anything to do with my problem. I don't know much about roms and flashing I don't even have a computer. So yesterday I turned my phone off to reboot it but then it wouldn't turn back on. It was stuck on a screen saying custom binary blocked by frp. I didn't do anything everything was fine til I restarted it. Can someone please help me fix this please???????? :(
[Android Q&A, Help & Troubleshooting] Trel:
Only solution I've seen to this is to use ODIN to restore to stock and start over. I haven't seen any alternative ways around this yet, though someone else may know more, as I don't typically use Samsung devices.
[Android Q&A, Help & Troubleshooting] Princess.:
Idk how to do that
[One (M7) Q&A, Help & Troubleshooting] snahad007:
My htc one m7 is on some type of gray screen while converting this to Google play edition i would like to get this problem solved

I am new to these root type of stuff so any info would help thanks...........

I tried to change my mid by following this steps: http://xdaforums.com/showthread.php?t=2322820

but it stopped at the step of grey screen.

what should i do?

My phone details:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.39.2000

(bootloader) version-baseband: N/A

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 6.23.651.10

(bootloader) version-misc: PVT ENG S-OFF

(bootloader) serialno: FA36FS900006

(bootloader) imei: ***************

(bootloader) meid: **************

(bootloader) product: m7_wls

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0720000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 3765mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: ENG

(bootloader) boot-mode: RUU

(bootloader) commitno-bootloader: 080b6f61

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

[IMG="Gray Screen Problem"]http://dl-1.va.us.xda-developers.com/2/6/9/9/7/6/0/IMAG0374.jpg?key=hM93Vmojh7YRl6y-IdP8uQ&ts=1449498979[/IMG]
[One (M7) Q&A, Help & Troubleshooting] alray:
First thing you should have done was to read the moderator warnings at post #1 of that thread you have linked. This guide is dangerous for your phone and there are now really easier and safer way to do this without any risk for your phone like explained in the OP and be me if you read the last pages of that thread.

2nd, your phone is a Sprint CDMA variant (M7WLS). You can't flash a M7_UL RUU (like the GPE version) on a M7WLS. The WLS variant doesn't have the same partition layout and modem as the M7_UL. So on your Sprint phone you can only flash sprint RUU. Converting your phone by changing the MID is only possible for the M7_U and M7_UL version.

3rd The gray screen is actually the eng hboot. Like explained in that guide, you can still use fastboot commands there to change your MID. But since this guide doesn't apply to your phone, what you need to do now is to reflash your stock bootloader over the eng bootloader which will get you out of this mess.

4th If you don't get fastboot connectivity at the gray screen, its probably because you didn't read the warning at post #2 neither. You have to use Windows 7 since newer versions of windows can't detect the phone on hboot 1.44 and below (the eng hboot is 1.39....)
[One (M7) Q&A, Help & Troubleshooting] snahad007:
Thanks a lot..... It worked successfully!
[XDA Assist] felice_pinto53:
Hi, I've a problem with this rom.

It's almost perfect, but often show up a message that is:

"Google Play Service has stop working".

Can I fix this?
[XDA Assist] Primokorn:
Hi,

Thanks for using XDA Assist :)

Did you try to wipe the app data from the system settings? Do you have compatible GApps?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] bingozingo:
Hi All ,

My phone S4 Mini I9195 is recognized by Odin but Kies can't recongnize it .

Be informed that I had a problem with my phone ,when I power up the phone just vibrate nothing appear on screen .
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Charlie:
I think your phone must be powered on to connect with Kies. So flash something with Odin to de-brick your mini, for example stock firmware.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] bingozingo:
I can't de-brick it because with odin stuck on initialisation
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] bingozingo:
please any advice
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Toufinious:
please try to be a bit more descriptive?

What happened before the problem occured? did you attempt to root/flash a rom/etc?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] bingozingo:
No,suddenly ,when I powered it it just vibrate so I wanted To root it but I can't .
[Fire General] TallGrassShort:
For clarity, this is for a person that is currently on 5.0.1, correct? This is to go from 5.0.1 to 5.1.1 while retaining root/TWRP, but this will not allow someone that is on 5.1.1 to access TRWP, right?
[Fire General] bibikalka:
Indeed, you have to have 5.0.1 so that you can boot into TWRP
[Fire General] Deuces:
copied update to AFH:

https://www.androidfilehost.com/?fid=24269982087012932

MD5: 8dfcc416a0b2c47fe384dd28f2ef18ed
[Fire General] julianpaul:
So once we're on this, they cant OTA us to 5.1.1 because we're already on it right? Now 5.1.2 ...
[Fire General] hp420:
the last step is to block OTA updates.......sooooo....;)
[Fire General] TallGrassShort:
So does anyone know what 5.1.1 offers over 5.0.1?
[Fire General] julianpaul:
No i meant even if ota is left enabled, there's no immediate risk.
[Fire General] Vlasp:
I will try to make a edited stock 5.1.1 ROM with Root, No Lockscreen Ads, etc.
[Fire General] Pond-life:
I was wondering that

Yeah but you had that cliffhanger 5.1.2 ending...

Sounds very useful :)

Will this work direct from 5.0.0? I see no reason it shouldn't but just checking.
[Fire General] si_na:
I'm also curious, does this also work for an unrooted/stock 5.0.0? (a brand new device) Has anyone tried?
[Fire General] Pond-life:
Seen someone mention on another thread that they've done it.

Which is handy as I've got to talk someone through this on skype later in the week when theirs arrives.
[Fire General] 87racer:
So even after booting this up you can get back to fastboot and use fastboot boot to get back into TWRP?

The new devices seem to be coming with 5.0.1 not 5.0.0.
[Fire General] gad42000:
Mine came with 5.0.0 which i bought on black friday. I didn't open the other boxes, but i assume they are the same.

What benefits will I get with an 5.1.1 upgrade?
[Fire General] si_na:
I have a 5.0.0 version (from before the black friday). Would be grateful to know if the instruction above works for it, cause I can't upgrade to 5.0.1 first anymore.
[Fire General] 87racer:
From the release notes on a 5.1.1 tablet:

Blue Shade - Makes everything ugly by removing blue (supposed to be better at night)

FreeTime Web Browser - Browser for kids (limits, curated content, tracking, etc)

Activity Center - More kid stalking, track what the are spending their time on

Curfew - Restrict kids from using tablet even when FreeTime is not in use
[Fire General] Pond-life:
How do you find the system directory in Explorer? All I'm seeing is the internal "sd card" and the actual micro sd card.

Not that I'm expecting a new update in the time it takes me to let it online and download a file browser on the tablet, but seems I'm missing something that could be handy in future. Thanks.

---------- Post added at 08:48 PM ---------- Previous post was at 08:46 PM ----------

Having just done it. Yep, sat in twrp atm.
[Fire General] 87racer:
interesting so the 5.0.1 preloader and uboot work just fine with the 5.1.1 system image just not the other way around...think I will just RMA that tablet rather than get SP Flash Tools to work.
[Fire General] Pond-life:
Well you can as you could download the 5.0.1 and install it through twrp, but if it's not needed it's somewhat pointless.
[Fire General] howzitnow:
I received one on October 21st that came with 5.0.0, I received one a week October 26th later that came with 5.0.1. That's from Amazon, I suppose ymmv if you got them at BestBuy or elsewhere.
[Fire General] DB126:
No. The techniques outlined in this thread are not applicable to your device as it started on FireOS 5.1.x vs 5.0.x. At present there is no way to directly root 5.3.1 although root can be maintained for those with an older 5.0.x bootloader. Can't downgrade your device below 5.1.2; it will brick.
[Fire General] alpenglow:
I manually updated HD 10 from 5.0.0 to 5.0.1.

Tried to use [boot twrp]. but it didn't go to twrp, but restarted normally.

ANY suggestions? Thank you all
[Fire General] DB126:
Wrong forum; ask here: http://xdaforums.com/hd8-hd10
[Fire General] Cephon:
I'n on 5.1.4, does this all still apply?
[Fire General] DB126:
You must first sideload 5.1.2 from the stock recovery menu as 5.1.4 can not be rooted.

http://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
[Fire General] Mor Hedroom:
Just a quick clarification for a simpleton:

To prevent further OTAs, should I rename the DeviceSoftwareOTA.apk file to DeviceSoftwareOTA.apk_ (just append the underscore) or rename the whole file down to just .apk_ ?

Thanks so much for this. As soon as I hear back, I'm going to go from 5.1.1 to 5.3.1 and will be happy to verify success.
[Fire General] DB126:
Goal is to change the name so the app can't/won't execute; how this is accomplished is your choice. Suggest appending an underscore as mentioned in this thread or simply change '.apk' to '.bak', '[.apk]' or some other arbitrary string you will recognize in the future. Just make sure it does NOT end in '.apk'.

Be aware instructions must be followed precisely to pull off an update without loosing root. Note a different file is recommended for those on FireOS 5.1.1. Carefully read the OP; ask if unsure.
[Fire General] sd_shadow:
you just need to change the file extension

e.g. .apk to .bak
[Fire General] Mor Hedroom:
Thanks very much - just wasn't sure how aggressive and/or flexible the firmware my be at parsing or repairing what would appear to it to be a damaged filename. Guess it's just like regular old Android and can be pretty easily fooled and won't magically repair itself.

Thanks again for the reminder on getting the right files for the FlashFire process. I do know that I want to keep the 5.1.1 bootloader for its easy temp root trick, and that FlashFire leaves no room for any screwups since it is an all-at-once solution. Get it right or start the tears. At least if I break it I can keep all the pieces, right?

I have read the OP several times and I'm prepared to give it a shot once I download things. Everything else has gone very well for me with this little tab - Rooting, Play Store, no ads, no updates, etc. I just want it to work well when all is said and done. Not trying to change the ROM or even the launcher. There are just a few quirks in 5.1.1 - the most annoying of which is the fact that every time I open an app from a folder on the bone-stock home screen, then close the app, the tab thinks I'm trying to change the name of the folder, puts a cursor on the name field and pops open the soft keyboard. Haven't found a way to stop that, and after searching around for a good while, haven't found anyone else complaining of it. Perhaps 5.3.1 will help. Worst case, if I hate 5.3.1 I'll pop it back down to 5.1.1 and start over.

Excellent. Thanks so much for the clarification, and also for your work here. I don't post often as I don't want to clutter threads. I just search and follow directions, and everything has been great, from three phones and about 8 tablets (3 of them KFFOWI, each on a different OS version!), never been steered wrong or bricked anything. Yep, I'm a searcher/reader.

Love this place and the great people that help keep it going. You people pretty much rock.

Funny story: I ordered a Fire this month, it was delivered already initialized (no language or wifi config screens on first boot) so it must have been a return. Best part was it came delivered with 5.0.1 -- in September 2016! Man, I wish all the bootloaders were like that one. So nice.

-Hedroom
[Fire General] DB126:
Boy, I wish more people followed that model! These forums are rich in detail thanks to the many helpful posts from dozens of contributors. Most questions have been answered before in some way/shape/form. A quick search will usually surface many relevant posts.
[Fire General] Mor Hedroom:
I could not agree more. The wealth of information ignored and sacrificed here on the sickly altar of tl;dr is appalling. Read, my friends, read!

Anyway, just wanted to confirm for those still on the fence; The FlashFire scenario works perfectly. Went from 5.1.1 to 5.3.1 with no issues, no hitches, no glitches. Seamless and flawless, just like bibikalka said here:

http://xdaforums.com/showpost.php?p=67872336&postcount=158

Full root, all apps, settings, and everything intact. Verified that the 5.1.1 bootloader is still in place with a hex dump like in the OP. FlashFire was so careful, the FlashFire app still popped up on my "recent" screen with a press of the square softkey. The only panic I had was my own fault after I realized I left the wifi on. During the first boot, I scrambled over to my router and powered it off while I killed the OTAs and ads.

After it booted and settled a few minutes, I renamed the OTA .apks (two of them, but I left the OTA UI app in place so I could see the version I'm on; I'm vain like that), then renamed the Offers .apk so no lock screen ads.

I love this place! Thank you for all the hard work of the contributors!

-Hedroom
[Fire General] fuzzynco:
Where can I get a .bin/.zip for just 5.3.1 (bootloaders and boot only); like the specials above for 5.1.1 and 5.1.2 bootloaders and boot?

I can run 5.3.2 on the 5.3.1 bootloaders & boot; I successfully ran the 5.3.2 /system with the 5.1.2 bootloaders & boot.

My new tablet came with 5.3.1 installed.
[Fire General] bibikalka:
I have not made that one yet. I guess without 5.3.1 BLs it'd brick ?

[MENTION=1311179]fuzzynco[/MENTION] - I've added the 5.3.1 BLs to post #1.
[Fire General] DB126:
To my knowledge the 5.3.1 bootloader has not been extracted and made publicly available by the OP. Probably a simple procedure; might even be able to flash a bootloader backup created in Flashify (something you could do being on 5.3.1). Hopefully can get a more definitive response from [MENTION=6680544]bibikalka[/MENTION]
[Fire General] fuzzynco:
I have fireOS 5.3.1 installed.

would a script like...

getprop("ro.product.device") == "ford" || abort("This package is for \"ford\" devices; this is a \"" + getprop("ro.product.device") + "\".");
show_progress(0.750000, 0);
#ui_print("Patching system image unconditionally...");
#block_image_update("/dev/block/platform/mtk-msdc.0/by-name/system", package_extract_file#("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
#package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/by-name/boot");
show_progress(0.200000, 10);
package_extract_file("images/lk.bin", "/dev/block/platform/mtk-msdc.0/by-name/UBOOT");
package_extract_file("images/tz.img", "/dev/block/platform/mtk-msdc.0/by-name/TEE1");
#
# Edify script to copy the correct preloader image
#

# check if production device
if (getprop("ro.boot.secure_cpu") == "1")
then
ui_print("Copying preloader_prod.img to boot partition 0 for secure device...");
package_extract_file("images/preloader_prod.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
else
if (getprop("ro.boot.secure_cpu") == "0")
then
ui_print("Copying preloader.img to boot partition 0 for unsecure device...");
package_extract_file("images/preloader.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
else
if ("0025001000000015" == read_file_str("/proc/idme/board_id") ||
"0025001000010015" == read_file_str("/proc/idme/board_id") ||
"0025001010000015" == read_file_str("/proc/idme/board_id") ||
"0025001010010015" == read_file_str("/proc/idme/board_id") ||
"0025001020000015" == read_file_str("/proc/idme/board_id"))
then
ui_print("Copying preloader.img to boot partition 0 for unsecure device...");
package_extract_file("images/preloader.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
else
ui_print("Copying preloader_prod.img to boot partition 0 for secure device...");
package_extract_file("images/preloader_prod.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
endif;
endif;
endif;

#
# Edify script to copy the correct logo image
#

ui_print("Copying logo.bin to LOGO partition ...");
package_extract_file("images/logo.bin", "/dev/block/platform/mtk-msdc.0/by-name/LOGO");

package_extract_file("META-INF/com/amazon/android/target.blocklist", "/cache/recovery/last_blocklist");
set_metadata("/cache/recovery/last_blocklist", "uid", 0, "gid", 0, "mode", 0444, "capabilities", 0x0);

work like the 2 you provided. I commented out the references to the system and boot partitions.

I figured that would only reload the 5.3.1 boot loaders.
[Fire General] bibikalka:
Well, just download a zip in post #1, extract this script, and do diff with yours, see if it's the same :D
[Fire General] steve8x8:
I can tell that the original scripts haven't changed since 5.1.1 came out,

$ find . -name updater-script | xargs md5sum | sort
43c50f70192032f9ab67a55db02e6a4e ./fireOS-5.1.1/META-INF/com/google/android/updater-script
43c50f70192032f9ab67a55db02e6a4e ./fireOS-5.1.2/META-INF/com/google/android/updater-script
43c50f70192032f9ab67a55db02e6a4e ./fireOS-5.1.4/META-INF/com/google/android/updater-script
43c50f70192032f9ab67a55db02e6a4e ./fireOS-5.3.1.0/META-INF/com/google/android/updater-script
43c50f70192032f9ab67a55db02e6a4e ./fireOS-5.3.2.0/META-INF/com/google/android/updater-script
43c50f70192032f9ab67a55db02e6a4e ./fireOS-5.3.2.1/META-INF/com/google/android/updater-script
e1471825dc27e525eb1b0d02cdfd053c ./fireOS-5.0.1/META-INF/com/google/android/updater-script

- which leads me to the assumption the same *modified* updater-script would still work - with replaced bootloader files, of course.

What I still don't get: whether people worry about extracting dangerous stuff to flash, instead of stripping the dangerous stuff from the original ROM package, to flash everything-but-the-bootloader (which I'd consider much safer as it doesn't touch the tripwires)... A modern ROM without bootloader files, and without bootloader installation script commands, would be completely agnostic of the system below and its bootloader specifics - it's just a running FlashFire you need to upgrade *to* a new version (no need to know where you're coming *from* anymore as long as you got root)... (Where am I wrong?)
[Fire General] bibikalka:
Big Lebowski [1998]

Walter Sobchak:
Am I wrong?

The Dude:
No you're not wrong.

Walter Sobchak:
Am I wrong?

The Dude:
You're not wrong Walter. You're just an asshole.

Walter Sobchak:
All right then.

;)

On a serious note, imagine stripping out bootloaders for each new update, uploading it to some hosting place (and these are large files we are talking about), and then having people download a new giant update with who knows what in it. It's quite a bit of traffic, and unpaid labor just moving these files around :(

Instead, Amazon serves as a perfect hosting location already, and we just change the bootloaders after the update puts in the new versions. So far I have not seen anybody suffer from not being able to update the bootloaders to the older versions they need. In fact, one can always just keep what they got with the each Amazon update, and say to the older bootloaders bye bye. This would also work most of the time, except when people screw up, and want to sideload a rootable version, but won't be able to.
[Fire General] steve8x8:
Thanks for calling me an a*****e. That's going to be the best birthday present for this year, I suppose.

You got me slightly wrong, btw: I didn't plan to setup another repository for pre-built fw images, just to provide a script that can be run on any stock fw, outputting a bootloader-less version.

My plans have changed, but I'll leave the idea behind.
[Fire General] BeeWall:
Could one use this method, but just flash system instead of bootloader, to downgrade 5.3.2.1 to a rootable os version?

EDIT: Nevermind, just realized this uses FlashFire, not adb sideload.
[Fire General] tech3475:
Sorry, I need some clarification on the bootloaders as I plan on upgrading a few Fire 7's to 5.3.2.1.

On my 5.0.1 fire 7, is it safe to flash the update using TWRP then flash the old bootloader using the provided zip along with supersu?

It is only unsafe to downgrade a device which has already been updated rooted or not (like my parents 5.3.1 Fire 7s rooted using kingroot)?
[Fire General] DB126:
Correct. Key is to flash the 5.0.1 bootloader immediately after FireOS 5.x.x is installed; do NOT reboot between steps. This will only work if the active bootloader is 5.0.0/5.0.1; device will brick if a higher bootloader is currently installed. There are no known benefits to 5.0.0 vs 5.0.1; recommend going with the latter.
[Fire General] Crashoverride1993:
If running flashfire 5.3.1.0 rooted would it be possible to install flash an all google android with flash fire and not brick it and if so whats the recommended one.
[Fire General] DB126:
https://xdaforums.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714
[Fire General] Hallo32:
Does the recovery decide, which FireOS version can be sideloaded?

5.3.1 root -> update with flashsfire to 5.4.0 -> sideload 5.3.1 is not possible.
[Fire General] DB126:
Bootloader (installed with FireOS) determines how far you can rollback without bricking the device. There are no rollback options for 5.3.1 as an updated bootloader was introduced with that release. Sideloading 5.4.x will install the bootloader introduced with FireOS 5.3.2.1 which establishes the new rollback floor.

At present there is no path to installing FireOS 5.4.x while retaining the 5.3.1 bootloader (theoretically possible but lacking 5.3.1 bootloader extract).
[Fire General] Hallo32:
Isn't the fourth file of the starting post the 5.3.1 bootloader?

But why can I not sideload the 5.3.1 with a 5.3.1 bootloader? Does the recovery do any version control?
[Fire General] DB126:
Yep - you are correct! Hadn't noticed (or more accurately remembered) the 5.3.1 bootloader had been extracted/posted. Sucks getting old. :)

So yeah, if you have 5.3.1 you can sideload an official 5.3.1 bin from Amazon which effectively refreshes the ROM (in contrast to a 'factory reset' which only wipes caches and the data partition while leaving the system partition and any corruption within it untouched). There is no benefit to using the 5.3.1 bootloader attached to the OP unless attempting an upgrade to FireOS while retaining root obtained while on 5.3.1.
[Fire General] Hallo32:
We should fix the bug very soon. ;)

That is the back door I would like to have still open.

Is it possible to modify the recovery partition without breaking the operation?
[Fire General] DB126:
Nope - bootloader remains locked so no touchy recovery partition. Typical outcome is outright failure although a few who attempted to flash TWRP ended up with either: 1) non-functional recovery; or 2) bricked device depending on path taken.
[Fire General] Hallo32:
Is the recovery signed or how does the boot loader detect the changes?
[Fire General] DB126:
Uncertain of the gory details. A simple attempt to flash a new recovery will typically fail due to missing permissions but that's easy to side step. More overt attempts yield the outcomes described in my previous post. Signed recovery makes sense.