Database Develop

[Q] where to get signed images?

Hi,
As I believe I need to reflash my chromecast using the original firmware, does anyone know where I can get it from?
(If your interested in why, please see below.)
I seem to have a bricked Chromecast that I'm trying to revive (black screen after the booting chrome logo),
I have soldered in the serial port and it seems to boot the normal image ok (see bottom for dump), I have tried both the normal and the recovery image, it performs the recovery okay, however the normal boot after recovery yields the same results.
Therefore I would consider the next step to reflash it, however it refuses to flash using the GTV released firmware, because the existing firmware is to new to allow for the exploit, I therefore believe that i need a current firmware which is signed by google to attempt recovery of the chromecast, I spoke to google about it and I was welcome to sent it back and get a replacement, however as I'm in Europe, it would be cheaper to just buy a new one, than to pay the postage.
P.S. I posted this in a non-QA forum, under the assumption that links would be of general interest to chromecast developer community, and therefore would be easier to find here, if moderators disagree, I apologize for the inconvenience of moving this post.
Normal boot:
s_init start. boot_strap=0x00000080 (source=NAND), boot_state=0x0
PG868: leakage=192 vcore=11 sysctl=59
Customer key found, loading customer key...
Loading Secure Customer Key Store is finished
Loading Secure Customer Key Store is finished
Finish loading Customer Key store
bootloader image verified, start...
eureka-b3 BG2CD [Aug 5 2013 10:54:27] ver:f07e92b-dirty
OTP s0x000000FF lkg curr=192 mAnd_randomizer_init_by_flash_type(chip_id = 0x2C48044AA500): !!! RANDOMIZED !!!
[FASTLOGO] init.
[FASTLOGO] Set CPCB1 output reso 8.[SHOWLOGO] start
showlogo_init_irq, Enable IRQ_dHubIntrAvio0(0x20) for cpu 0
[FASTLOGO] done.
fts: v94 loaded from 0x00174000
[SHOWLOGO] stopped
Boot normal GTV image
fts: record v95 commited @ 0x00178000
Uncompressing Linux... done, booting the kernel.
Click to expand...
Click to collapse

bse10093 said:
Hi,
As I believe I need to reflash my chromecast using the original firmware, does anyone know where I can get it from?
(If your interested in why, please see below.)
I seem to have a bricked Chromecast that I'm trying to revive (black screen after the booting chrome logo),
I have soldered in the serial port and it seems to boot the normal image ok (see bottom for dump), I have tried both the normal and the recovery image, it performs the recovery okay, however the normal boot after recovery yields the same results.
Therefore I would consider the next step to reflash it, however it refuses to flash using the GTV released firmware, because the existing firmware is to new to allow for the exploit, I therefore believe that i need a current firmware which is signed by google to attempt recovery of the chromecast, I spoke to google about it and I was welcome to sent it back and get a replacement, however as I'm in Europe, it would be cheaper to just buy a new one, than to pay the postage.
P.S. I posted this in a non-QA forum, under the assumption that links would be of general interest to chromecast developer community, and therefore would be easier to find here, if moderators disagree, I apologize for the inconvenience of moving this post.
Normal boot:
Click to expand...
Click to collapse
If you had the exploitable bootloader, I would refer you to my thread I made awhile back about debricking, but if yours is updated, I think all you can really do is send it back to google, or buy a new one. To my knowledge, there has been no leak of an official signed USB image.
What you can try though is booting the chromecast into recovery (no idea how you can do that if its "bricked"), and have a jump drive with one of the official OTA Zips on it, named ota.zip. The chromecast recovery, if unable to find a update at /data/, will check an external jump drive.
Here is the link for the Official 13300 update. http://dl.google.com/googletv-eurek....1f63ef63d1f43c6222116806e5bea38a47e9f124.zip

tried recovery, but no luck
Thanks for your suggestions, I've tried to see if I can get it to load the software either by corrupting the boot (touching the memmory without the shield after a few tries seems to be enought to cause corruption and thereby make it try to boot from usb, however seems to fail locating the image it may however just be a matter of me having to put it in there in a certain way.
The device seems to have bricked in a weird way, that is the recovery process seems to run without error and so does the normal boot process until the very end when it is supposed to switch from the spinning chrome logo into the chromecast desktop, it just switches to the black screen.
I was able to start the recovery, but I assume that it must have an existing ota.zip in /data/, as it doesn't seem to check the jump drive.
ddggttff3 said:
If you had the exploitable bootloader, I would refer you to my thread I made awhile back about debricking, but if yours is updated, I think all you can really do is send it back to google, or buy a new one. To my knowledge, there has been no leak of an official update.
What you can try though is booting the chromecast into recovery (no idea how you can do that if its "bricked"), and have a jump drive with one of the official OTA Zips on it, named ota.zip. The chromecast recovery, if unable to find a update at /data/, will check an external jump drive.
Click to expand...
Click to collapse

Have you tried doing a factory reset on the chromecast? by button, or the setup application?

bse10093 said:
Thanks for your suggestions, I've tried to see if I can get it to load the software either by corrupting the boot (touching the memmory without the shield after a few tries seems to be enought to cause corruption and thereby make it try to boot from usb, however seems to fail locating the image it may however just be a matter of me having to put it in there in a certain way.
The device seems to have bricked in a weird way, that is the recovery process seems to run without error and so does the normal boot process until the very end when it is supposed to switch from the spinning chrome logo into the chromecast desktop, it just switches to the black screen.
I was able to start the recovery, but I assume that it must have an existing ota.zip in /data/, as it doesn't seem to check the jump drive.
Click to expand...
Click to collapse
I believe it will try to install a file named ota.zip on the root of a flash drive if it doesnt find an ota on internal storage.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

factory default
ddggttff3 said:
Have you tried doing a factory reset on the chromecast? by button, or the setup application?
Click to expand...
Click to collapse
Yes I've tried it and it runs without errors, reboots however when back in normal boot mode it still shows the black screen instead of chromecast desktop.
P.S. maybe I should mention that the chromecast ad-hoc network also comes up, unfortunately though that doesn't seem to help.

doesn't seem to activate usb key
tvall said:
I believe it will try to install a file named ota.zip on the root of a flash drive if it doesnt find an ota on internal storage.
Click to expand...
Click to collapse
I tried renaming, however when starting recovery with the usb key containing the official 13300 renamed as ota.zip, it never has any disk activity on the usb key, however I can verify that it can read the key from the bootloader as it detect the key, but fails the signing step

Return MJ5 to Stock after Kingo Root

I had a heck of a dilemma this past week.
I have the N900A that I rooted using Kingo Root. No safestrap or new roms, just rooted. I obviously had the 'Custom' icon.
At day 20, my phone wouldn't charge any more or be recognized by USB. I tried everything. Factory reset, cleaned the port, cleaned the cables, new cables. Nothing helped. And it would have to be warranty exchanged through AT&T, but the warranty was voided because of root. I couldn't use Kingo to unroot, because the PC wouldn't recognize it.
I was able to find a workaround, using this:
http://forum.xda-developers.com/showthread.php?t=2559715
In fact, I really only used the third step. I didn't download or flash the rom. By some miracle, the PC would connect to the phone when it was in download mode. I used Odin to flash those four files, rebooted, and the custom icon was gone.
I'm hoping that this has removed all trace of root from the phone. The knox counter is still at zero.
I thought I would post this in case anyone else had a similar problem.

its on here too
http://forum.xda-developers.com/showthread.php?t=2559715

Return to stock
steveh_131 said:
I had a heck of a dilemma this past week.
I have the N900A that I rooted using Kingo Root. No safestrap or new roms, just rooted. I obviously had the 'Custom' icon.
At day 20, my phone wouldn't charge any more or be recognized by USB. I tried everything. Factory reset, cleaned the port, cleaned the cables, new cables. Nothing helped. And it would have to be warranty exchanged through AT&T, but the warranty was voided because of root. I couldn't use Kingo to unroot, because the PC wouldn't recognize it.
I was able to find a workaround, using this:
http://rootzwiki.com/topic/110386-return-to-stock-mj5-works/
In fact, I really only used the third step. I didn't download or flash the rom. By some miracle, the PC would connect to the phone when it was in download mode. I used Odin to flash those four files, rebooted, and the custom icon was gone.
I'm hoping that this has removed all trace of root from the phone. The knox counter is still at zero.
I thought I would post this in case anyone else had a similar problem.
Click to expand...
Click to collapse
Ok so, only doing step 3 returns the device to complete stock? I would do all the steps, but I don't really understand all of them.

asilva54 said:
its on here too
http://forum.xda-developers.com/showthread.php?t=2559715
Click to expand...
Click to collapse
Thank you, didn't see that when I searched last time.
ZOMBIExM4STER said:
Ok so, only doing step 3 returns the device to complete stock? I would do all the steps, but I don't really understand all of them.
Click to expand...
Click to collapse
I believe the rest of the steps serve to load the MJ5 version ROM onto the device (in case you've installed a newer one or something). Since I already had the stock ROM, they proved unnecessary for me. I just used Odin to flash those 4 files and since the icon disappeared, I stopped there.

steveh_131 said:
Thank you, didn't see that when I searched last time.
I believe the rest of the steps serve to load the MJ5 version ROM onto the device (in case you've installed a newer one or something). Since I already had the stock ROM, they proved unnecessary for me. I just used Odin to flash those 4 files and since the icon disappeared, I stopped there.
Click to expand...
Click to collapse
I'm on stock too, I want to do this because I'm having problems with the keyboard. The whole process is really confusing to me, do you think you can help me out?

ZOMBIExM4STER said:
I'm on stock too, I want to do this because I'm having problems with the keyboard. The whole process is really confusing to me, do you think you can help me out?
Click to expand...
Click to collapse
I will try, but I am not an expert by any means. I tinker, but hopefully these other more experienced guys will chime in if I say something incorrect.
1. Download odin from here: http://www.firmware-files.com/download.php?id=1&token=QDXtLX5r3hLhxpTt604CYR6zP9twKSmr
2. Extract odin to a folder on your computer
3. Download these four files:
http://www.firmware-files.com/download.php?id=8&token=1QMc777QYjZgceInVMKs1HlcxAWv2wrU
http://www.firmware-files.com/download.php?id=7&token=6AfQkrv4S1mjr2oClQdwHp62lZpT8BK5
http://www.firmware-files.com/download.php?id=6&token=rXopUUlOTAGrBAQfksBLl1lKu52xIjl0
http://www.firmware-files.com/download.php?id=15&token=5CYaBqGOCoJSQMM6K7WECGlLDK4NYWTT
4. These four files will be zipped. You need to extract the zip files somewhere onto your computer. Each file should have a .tar.md5 extension once you extract them.
5. Power off your phone. Put it into download mode. To do this:
Power off your phone completely'
Hold down the home button, volume down button and power button all at the same time
When the screen comes on, let go of the buttons
It will give you a warning. Press the volume up button to proceed to download (odin) mode.
6. Run the Odin3 v3.09.exe application (that you extracted in step 2)
7. Now that odin is running and hopefully connected, you need to specify the four files that you extracted to be downloaded. You should end up with a screen that looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. Click start and let it run until it is finished. Once it is finished, hold down the power button to power off your phone then do the same to turn it back on. The custom icon should be gone.

First thing I do after rooting is Wanam and turn off the Custom - just in case something like this happens. If the phone later blows up, factory reset if possible and walk it in for an exchange. Then if, when it blows up, even Odin can't see it, there's still no lock on the screen.

Rukbat said:
First thing I do after rooting is Wanam and turn off the Custom - just in case something like this happens. If the phone later blows up, factory reset if possible and walk it in for an exchange. Then if, when it blows up, even Odin can't see it, there's still no lock on the screen.
Click to expand...
Click to collapse
Doesn't factory reset delete the Xposed framework?
With AT&T you can't do a walk-in exchange after 14 days - pretty scary to mail it in for exchange and risk a $650 charge when they discover you rooted it.
I had the icon turned off with Wanam, but it came back.

steveh_131 said:
Doesn't factory reset delete the Xposed framework?
Click to expand...
Click to collapse
I could probably write an accounting program for an agency as large as the US government (or have fixed the health insurance site - doing something for half a century does pound some knowledge into even rock hard heads like mine), but when it comes to Android, I'm one of the learners, not one of the teachers. You know the answer to this question better than I do. I'd assume it does. I've made a lot of stupid assertions over the years, so ...
I downloaded a course that I may start reading one of these days, so I might yet learn enough to write a "Hello, World" app for Android. (Programmers know what I'm talking about - the difference between being able to develop a program and being able to code something to run in a particular environment - and the only internal environment I know in Android is where the battery and cards go.)
With AT&T you can't do a walk-in exchange after 14 days
Click to expand...
Click to collapse
SSSSSSHHHHHHHH!!!!!!! You weren't supposed to tell them that. I hope they didn't read this thread, and I hope the very nice lady who gave me the phone I'm using now doesn't get into trouble. (I'm not talking about walking in and saying "I don't like this phone, may I have a different one, please?" I'm talking about walking in during the warranty period and saying "could you please make my phone work?" and being told that they'll have to give you another phone. The only thing I'd trade my N3s for is N3s with unlocked bootloaders. I just want to see something other than comets revolving around Samsung's name.)
I had the icon turned off with Wanam, but it came back.
Click to expand...
Click to collapse
Mine stayed off - for the 3 or 4 days that the hardware didn't die on me. Then ... well, maybe Samsung has a way to read melted silicon, or whatever it did to make itself electrically invisible, but I'm not going to worry about it.

Wanam will keep the icon hidden but once you factory reset the phone I believe it deletes the xposed framework and the icon comes back.
I could be wrong about that, but that is my understanding.
I don't think you'd ever fool the warranty department that way, unfortunately, which is why I used this method.
Sent from my SAMSUNG-SM-N900A using Tapatalk 2

after doing just step 3 did you run a root check to see if that was gone? also what was the state of your phone after only doing step 3....meaning custom on dl mode and lock on boot screen....just wondering cause the files are so small to think that it would completely return to stock (like day 1)

ryant100 said:
after doing just step 3 did you run a root check to see if that was gone? also what was the state of your phone after only doing step 3....meaning custom on dl mode and lock on boot screen....just wondering cause the files are so small to think that it would completely return to stock (like day 1)
Click to expand...
Click to collapse
No custom and no lock. I didn't run a root check, not even sure how.
The files are small because you're not flashing an entire ROM. My ROM was still stock.

Well, I screwed up trying to root. And I'm willing to pay someone to help me fix it.

After a series of poorly judged flashes and (eventually) factory resets in the name of acquiring root, I am left with a stock S6 that gets no service whatsoever. Knox is tripped. The phone shows 5 bars but will not connect to 4G, GSM, CDMA, nor will it send/receive anything unless it's connected to Wifi and uses wifi calling.
I've been trying to fix this since 11pm last night and I am extremely frustrated. I would love to pay someone who has a clear understanding of these things to hold my hand through getting this thing working again. I have passed the point where my skills can help me.

Hi do you have facebook
Sent from my SM-G800H using Tapatalk

Have you put in your phone companies apn settings ?

Have you tried to Odin back to stock? It sounds like you flashed a custom recovery; what exactly did you do?

Yes, the APN settings are correct. I entered them manually in a second profile, but they were prepopulated as well. Neither makes a difference. I get "Not registered on network" when I try to make a call. When I try to have the phone detect TMobile's network, it says "Unable to select network. Select automatically".
The big issue is, I'm fairly certain the first thing I flashed was not meant for this phone...smh. I was able to Odin back to stock. Before and after multiple factory resets and cache wipes (though no settting for Dalvik cache in recovery...does this mean anything?) everything works fine except I have no service.

Try and toggle Airplane mode on and off? Also if you were on Wifi with Wifi calling disable both of those for the time being. Last case would be to odin factory firmware.

yes, i've tried that. i've tried removing the sim card for a few minutes to no avail.
with wifi and wifi calling on, the phone functions as normal but as soon as that's off, everything stops working.

I don't trust Odin to wipe everything it should.
Download a rooted stock rom. Then go into recovery, mount /system and wipe /system, cache & data, then flash the rom. Finish the setup wizard and try to make a call without wifi. If you cannot, verify APN is correct.
You could have a bad sim card. Sim cards die just like any other piece of electronics. Go to T-Mobile and swap sim cards, they should do it for free.
Edit: I just realized you are probably still on stock recovery. Root your system, flash twrp, then nuke the phone in recovery and start from scratch.
I assume you already tried restoring a nandroid. If that doesn't work and you can't make calls after restoring via Odin or flashing another rom, then you may have corrupted the EFS partition. The only way to recover from that is if you backed up your original EFS partition. A lot of people don't bother, but it is a critical step before flashing your first mod.

..

thank you so much for the advice. i'm trying this now.

OMGitsAlize said:
Have you put in your phone companies apn settings ?
Click to expand...
Click to collapse
socal87 said:
Have you tried to Odin back to stock? It sounds like you flashed a custom recovery; what exactly did you do?
Click to expand...
Click to collapse
Saafir said:
Wouldn't hurt to give Update Profile a go under System Update too.
Click to expand...
Click to collapse
this option does not exist for me

sublimaze said:
I don't trust Odin to wipe everything it should.
Download a rooted stock rom. Then go into recovery, mount /system and wipe /system, cache & data, then flash the rom. Finish the setup wizard and try to make a call without wifi. If you cannot, verify APN is correct.
You could have a bad sim card. Sim cards die just like any other piece of electronics. Go to T-Mobile and swap sim cards, they should do it for free.
Edit: I just realized you are probably still on stock recovery. Root your system, flash twrp, then nuke the phone in recovery and start from scratch.
I assume you already tried restoring a nandroid. If that doesn't work and you can't make calls after restoring via Odin or flashing another rom, then you may have corrupted the EFS partition. The only way to recover from that is if you backed up your original EFS partition. A lot of people don't bother, but it is a critical step before flashing your first mod.
Click to expand...
Click to collapse
okay, i do think it's possible that i corrupted the EFS partition. however, in download mode, the IMEI number it displays is correct.
i am able to get the phone rooted and twrp installed, but once i try to flash the rooted stock rom, i get a "error executing updater binary in zip". not sure how to proceed.
i may abandon the phone altogether and just order an insurance replacement :-/

postmastergeneral said:
okay, i do think it's possible that i corrupted the EFS partition. however, in download mode, the IMEI number it displays is correct.
i am able to get the phone rooted and twrp installed, but once i try to flash the rooted stock rom, i get a "error executing updater binary in zip". not sure how to proceed.
i may abandon the phone altogether and just order an insurance replacement :-/
Click to expand...
Click to collapse
With knox tripped gooood luck. Also, did u have an EFS backup?

That error message means the rom zip is looking for a different device code than the one you are trying to flash it on. Where did you get the rom file? Are you sure it is correct for your S6?

dial *#0011# and post a screenshot for me. I can help you.

Sunderwear said:
dial *#0011# and post a screenshot for me. I can help you.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THANK YOU

Pm. I'll help you

Any resolution? I am curious to know what exactly happened and what fixed it.

sorry for not PMing you. i got frustrated and stubborn and just ordered a new phone.

postmastergeneral said:
sorry for not PMing you. i got frustrated and stubborn and just ordered a new phone.
Click to expand...
Click to collapse
I feel bad for you - but very curious about one thing - I thought I read the thread carefully and never noticed a response to the question - "Did you try to odin back to Stock?"
Samsung phones are amazingly resilient - and under most conditions (unless you the phone is really totally FUBARed ) odining back to stock cures 99% of all problems - at least that I have seen. And except in one instance with the NOTE 3 (after it's initial release) Odining the stock rom usually fixes the problem every time. The note three was an unusual circumstance in my memory - and it happend to a bunch of people - I actually screwed up two phones and returned them both to get replacements - Odin would not fix the problem because one of the particians or maybe all of them had been corrupted) but you had an IMEI where I did not - so I don't think that was your issue (although, I may be wrong)
anyway, I can understand your frustration - I have been there my self - but usually cooler heads (the people at XDA) have helped me to find the solution that eventually worked - did you try to ODIN back to Stock? If that did not work then returning the phone may have been your only option - but I would love to know if you did try that option?

Bricked phone.

Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.

Shinnazuka0411 said:
Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.
Click to expand...
Click to collapse
For a device that was format all. Will need more partitions than are in that package you tried. Also I have tried to work with someone else who had the 8gb size device, we could not get past that error.
I do recall that the last last person got a new board for his phone and pulled the images from it to share. There is a link in the main thread somewhere. But , well even when he tried to restore his own backup from good device to the one with do error, it did not work.
NVM
I remembered it wrong. He tried to pull it, but could not do it.
Look through this thread. Maybe you can try to follow the advice I gave him, and it may work for you.
https://forum.xda-developers.com/r1...-blu-r1-hd-t3440261/post76482224#post76482224

Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV

Shinnazuka0411 said:
Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV
Click to expand...
Click to collapse
There is now a "repair rom" listed in an mtk support group I try to follow. I have not checked it out yet, but maybe it will help. Let me open this on PC to search for the link
this one was labled v6.4 firmware http://www.mediafire.com/file/6kys9896445l5sm/SP_Flash_Tool_BLU_R0010UU_V6.4_Firmware.zip/file
this is labled as a repair firmware http://www.mediafire.com/file/il54pxuvpkargtr/BLU_R1_HD_R0030UU_REPAIR_MT6735.rar/file
I would have you look at those , first i suppose.
if it does not work I do have backups made from miricle-box, but they are not uploaded anywhere right now.

Real appreciated, will keep you updated, if anything works ill post it here.

Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL

Shinnazuka0411 said:
Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL
Click to expand...
Click to collapse
all I can do is share the backup from miricle-box that I have.
https://www.androidfilehost.com/?fid=5862345805528042536

Just trying to catch up, so bricked phone that wont format correct? Do you have twrp on it?

mrmazak said:
all I can do is share the backup from miricle-box that I have.
androidfilehost/?fid=5862345805528042536
Click to expand...
Click to collapse
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??

TavoStyle said:
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??
Click to expand...
Click to collapse
This is from 16gb so the R0030uu

mrmazak said:
This is from 16gb so the R0030uu
Click to expand...
Click to collapse
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

TavoStyle said:
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
Click to expand...
Click to collapse
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\

mrmazak said:
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\
Click to expand...
Click to collapse
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)

TavoStyle said:
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)
Click to expand...
Click to collapse
Most important part (custom build number) is missing from screen shot.

mrmazak said:
Most important part (custom build number) is missing from screen shot.
Click to expand...
Click to collapse
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig

TavoStyle said:
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig
Click to expand...
Click to collapse
so your build number is 6.6
you may be able to unlock.
But is phone still alive?

mrmazak said:
so your build number is 6.6
you may be able to unlock.
But is phone still alive?
Click to expand...
Click to collapse
My phone is stuck in the BLU logo

TavoStyle said:
My phone is stuck in the BLU logo
Click to expand...
Click to collapse
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\

Bricked BLU R1 HD
mrmazak said:
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\
Click to expand...
Click to collapse
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA. I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone. I am trying to install twrp but when I power on my device it is stuck on the boot loading screen. I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Tried using adb commands but when I connect to the phone and run adb commands it says no authorisation.
If I can install twrp on the device then I will be able to install the rom from rootjunky, not sure if you require more info.
Awaiting your ananlys
Kind Regards

ismailf007 said:
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA.
Click to expand...
Click to collapse
The latest ota blocks the use of sp flash tool. And the kernel exploit used previouls. But now there is new exploit. But you cannot boot so that is mutt point now
ismailf007 said:
I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone.
Click to expand...
Click to collapse
Did you only format the data partition or whole device.?
ismailf007 said:
I am trying to install twrp but when I power on my device it is stuck on the boot loading screen.
Click to expand...
Click to collapse
This confuses me. You just said you had twrp already. Now you have trouble to I stall it.
ismailf007 said:
I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
Click to expand...
Click to collapse
Did you use / try volume up?
ismailf007 said:
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Click to expand...
Click to collapse
From what you say.
1. You had working phone with SU root.
2. You have twrp installed
3. You wiped / formated with twrp
4. You now only boot to a logo screen. No recovery, or bootloader?

General [CLOSED] --

USE UPDATED POST, HERE!
THIS POST IS NOW ONLY REFERENCE ONLY - WILL BE DELETED SOON.
Well I figured I'd make a quick How-To on how I successfully Carrier/Sim unlocked my Samsung Galaxy S21 Ultra 5G running the NEWEST Android update on bootloader 5 (USQU5BULJ)released in January of 2022.
***This does NOT trip Know and does NOT require a root or a paid service. ***
****Also Note - This is the process I took, you may find some of these steps are not needed but for the purpose or recreating my results, I'll be posting my exact process.
****This has ONLY BEEN TESTED ON SNAPDRAGON BASED SAMSUNG GALAXY S21 ULTRA 5G SM-G998 U & U1, if you try it on a different model or phone you may (and likely will) receive different results!!!!
Here's what you'll need:
•ANY (activated or not) Sim from the carrier you wish to switch too.(or a way to replicate the carriers cert from one)
•A computer
•Patched Odin
•BOTH the NEWEST U & U1 ROMs/Firmware - theres a full post on these and how to flash them here on XDA (Reminder for myself or mod to link it) or visit SamFW.com, it has both Odin and the ROM/Firmware files you will need.
•Android ADB platform tools (You can find them on the official Android Developers page here or use any ADB software of your choice, fastboot is not required or used in this process.(Google "Android Developer Platform Tools" to get them from the official Android devs page. )
STEP 1:
So let's presume you have a Verizon or T-Mobile carrier locked phone, if you look at your baseband, which you can find in Settings > About > Software Info, you should see this "SM-G998Uxxxxxxx"
*****IF YOU SEE "SM-G998U1xxxxxxx" STOP - Skip to step 2******
Head over to your preferred site to get stock Samsung Roms (Refer to link above if you don't know where to find) and download the U1 XAA rom and the U rom of the CARRIER YOU WISH TO USE. IMPORTANT! MAKE SURE YOU DOWNLOAD THE "U" ROM FOR BOTH THE CARRIER YOU WISH TO SWITCH TO AND THE U1 UNLOCKED ROM.
Put you device in download mode (Hold Vol up and Vol down and plug in the USB, which should be connected to your PC and now your phone at this point.)
Flash the U1 XAA Rom, place appropriate files in appropriate places in Odin, when you get to CSC, DO NOT use the "HOME_CSC" use the other.
Leave the rest of Odin settings alone and hit Start, wait for it to finish and reboot.
Step 2:
Once the phone boots, return to Settings>About>Software and confirm you are using the XAA rom by looking at Service Provider Software Version and it should say something like "SM-G998U1_XAA blah blah blah" you just want to see the U1 and XAA.
Now put in the Sim from the carrier you desire. A pop-up should appear prompting you to restart your device. Follow the prompt.
!MOST IMPORTANT STEP!
BEFORE the device fully restarts, force it into RECOVERY MODE, I was able to achieve this by holding the power and Vol Down buttons at the same time, starting to hold the directly after the "Samsung" Logo fades away upon initial restart. If you have trouble getting into recovery please comment below.
Once in recovery, use the volume keys to navigate to "Clear Cache" select and execute. Now go to Factory Data Reset/Wipe, select and execute. It should be the option directly above "Clear cache".
Once done, go up to "Reboot to Bootloader", Select, Execute.
AGAIN, Very Important step,you MUST interrupt the boot process again and force the phone BACK into download mode this time, so once the phone attempts to reboot, you need to hold the Vol Down and Vol Up buttons at the same time and the USB MUST be already plugged in.
We should now be back in download mode and be on the U1 rom. We have verified all of this in the steps above.
STEP 3:
Now it's time to flash the ROM from the carrier you wish to use. Make SURE you have a Sim from that carrier inserted during this process. It doesn't need to be a working or activated Sim, just simply one from the carrier you wish to have your S21 work on.
Flash all items as you did earlier, but using the "U" ROM for your desired carrier as described above. Same deal with CSC, DO NOT use the "Home_CSC"
BE SURE that you use the USERDATA file if there is one for your carrier. Very important to have the phone working properly.
Start the Odin flashing process.
Phone will Auto-Reboot.
Done!
You should now be on the carrier you wish to use. This can be (in theory, test at own risk) replicated for ANY carrier supported by Samsung, and, I should soon find out if it will lead to what my original goal was, a bootloader unlock on the QualComm SnapDragon variant of the S21 and future Galaxy devices.
If you have any issues please comment below.
PoC, results after doing above process.
Good luck.
-k0mrade
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

There are some parts of my tutorial that are not well expressed and may be misleading. Please don't hesitate to post in comments if you need clarity.

IMPORTANT!!! I LEFT OUT ONE MAJOR STEP! ************ ----- BETWEEN STEP ONE AND STEP 2 - After you do the factory data reset/Wipe cache -> reboot to Bootloader -> force into download, you need to flash the U1 rom BEFORE putting in your desirced carriers SIM, then reboot, let phone fully boot, THEN insert your desired carriers SIM -> restart phone-> interrupt boot by forcing into recovery and repeat factory data wipe and cache wipe and reboot bootloader -> interrupt Boot Process again, but into Download Mode -> Flash your desired "U" carrier Firmware (must be same carrier as the SIM you put in as described above). -> Done.

And when/where does one need to use the required ADB-Tools?

tested and work only on S21 ULTRA 5G SM-G998 U & U1
thank you

OnnoJ said:
And when/where does one need to use the required ADB-Tools?
Click to expand...
Click to collapse
Lol this is likely one of those steps thats unneeded. i cant remeber off the top of my head why exactly i added that in. But it wont hurt to have the drivers, thats for sure.

Ive made a (Slightly) more clear post, hopefully better detailing this, Here. Mods may close this thread as they feel free but i will leave it up as a resource for the time being.

How many different devices have you tested this on?

iBowToAndroid said:
How many different devices have you tested this on?
Click to expand...
Click to collapse
ive just finished doing it on my 6th one device, 4 were Verizon 1 was Tmobile and 1 was ATT. I seem to be able to replicate this process over and over again so far with no issues so far, but i am making sure to update each device manually via odin 1st to latest u1 Firmware first as described above.

K0mraid3 said:
ive just finished doing it on my 6th one device, 4 were Verizon 1 was Tmobile and 1 was ATT. I seem to be able to replicate this process over and over again so far with no issues so far, but i am making sure to update each device manually via odin 1st to latest u1 Firmware first as described above.
Click to expand...
Click to collapse
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked

iBowToAndroid said:
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked
Click to expand...
Click to collapse
thats essentially the point of going from u to u1 then back to u after you booted atleast once into u1 with the desired carriers sim, somewhere along in the process of interrupting the bootloader and flashing the carriers U Firmware its overwriting the system policy. Theres a hole in here somewhere im positive. still trying to pin point exactly where this weakness lies.

iBowToAndroid said:
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked
Click to expand...
Click to collapse
End Game is to find a BL exploit to force enable OEM Unlocking on these qcomm s21s.

K0mraid3 said:
End Game is to find a BL exploit to force enable OEM Unlocking on these qcomm s21s.
Click to expand...
Click to collapse
You're definitely not going to find that, as that's not related to SIM unlocking whatsoever

iBowToAndroid said:
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked
Click to expand...
Click to collapse
And sorry to answer your initial question, yes, verfied carrier lock, getting errors like this, see attached.

iBowToAndroid said:
You're definitely not going to find that, as that's not related to SIM unlocking whatsoever
Click to expand...
Click to collapse
I like a challenge

This "temporary" thread is now closed. Main thread is here.