WARNING!!!!!Use of the following has been know to cause bricks and/or loss of functions in most of the devices it was attempted on. Because of this, the Thread was permanently closed. However the files will remain to assist in further development. Additionally, there is no promise if any of the links still work. So if you choose to mess with these files, you do so knowing it will probably brick your device.
Moscow Desire, XDA Moderator*******************************************************************************
[Pudding]
WARNINGS: READ ALL OF THIS BEFORE CONTINUING
1. All phones You most likely will lose 4g data connectivity from using this, hopefully a workaround is on the horizon.
2. All phones This has received limited testing, use at your own risk and accept that there may be a risk of hard bricks now or in the future (Unless you get your SBK.)
3. All phones Charge your phone, all the way please.
4. Use at your own risk. Have a backup phone, insurance plan or other means of recovering from a possible brick or loss of functionality. You are using experimental software at your own risk.
Works/Does not work list
Sprint en/us 45.2.5: Warning: Loss of 4g connectivity very likely
Electrify 2.3.5: Danger: Untested, I do not own one and cannot test
Click to expand...
Click to collapse
Updates
8/30/2011 Added stock recovery image for those wishing to use pudding remover.
8/25/2011 Pudding remover added. This restores your stock bootloader. 4G will be restored but your phone will be locked again. This is only the bootloader, so system changes will not be removed (root, recovery, program data, etc). Having the custom recovery still installed with the locked bootloader may cause problems (soft-brick, you will need to use full sbf or re-unlock and flash back the stock recovery). will cause you to soft brick. You will need to reflash the unlocker to recover and either leave it unlocked or restore the stock recovery and use the pudding remover afterwards. Thank you tuxy for being the only one basically willing to test this.
8/16/2011 Just a quick update on the 4g issue, most likely this will go unresolved until your kernel source is released and someone with the appropriate skills in kernel hacking fixes your ATAGS passed by the bootloader. For now you can either be unlocked and use 3g, or locked and use Wimax/4g. Pick your poison, at least neither is a permanent thing.
Click to expand...
Click to collapse
Who does/doesn't need this.
You need this if:
1) You need to flash custom single partitions such as system, osh, boot.img, recovery, or data.
2) Mainly for testing custom kernels, see number one.
3) You have a real ROM with a custom kernel, like CM7 or MIUI, and want to flash it.
You don't need this if:
1) Number one in the last section doesn't make any sense to you or sounds like gibberish.
2) You wanna show your friends how much cooler or better than them you are.
3) You just want to install P-ROMs and Themes.
Click to expand...
Click to collapse
You want pudding for Photon? There is pudding in space too!
Pudding:
http://diamantephoto.com/photon_pudding.rar 1mb bootloader only
Fastboot:
Use this to unlock after flashing pudding sbf (not available), also to flash custom partitions.
Windows: Moto-fastboot for windows thanks to romracer. Direct Download Link
Linux/Mac: Moto-fastboot for linux in several flavors thanks to eval-.
RSD/Drivers/SBF_FLASH:
You may need to reinstall drivers after the unlock.
RSDLite 5.5 Download
http://mophoforum.com/Roms/rsdanddrivers.zip
64bit windows drivers
SBF_FLASH(*nix/Mac)
Pudding remover:
Directions:
1) Make sure you are on the stock Recovery. If not, flash the image I provided below using this command:
Code:
fastboot flash recovery stock_recovery.smg
2) Flash the nopudding4u sbf using RSDLite or sbf_flash.
3) Done
http://www.multiupload.com/A4KCLBTL3K - 3.6mb stock recovery image from CM5
http://diamantephoto.com/photon_nopudding4u.rar - 1mb bootloader only, stock locked bootloader. For those of you who want a quick way to return to 4G.
Howto:
Is your phone fully charged? This should be first thing you check whenever you flash anything.
0) Back up all your apps and anything else you want to keep that is stored in /data, YOU WILL LOSE ALL FILES IN /DATA
1) Flash the pudding sbf file via sbf_flash(*nix/Mac) or RSDLITE(Windows).
2) Get moto-fastboot in your $PATH or at least in the same directory as the command line you open.
3) Open a command line or well, linux users know what to do, in the folder with pudding.
4) Type moto-fastboot oem unlock
5) Look for the UNIQUE ID number and copy it, use copy or your fat fingers might mistype it.
6) Type moto-fastboot oem unlock YOUR_UNIQUE_ID_THAT_YOU_JUST_COPIED
7) Enjoy!
Here is a picture of the steps on a windows command line (yes, I renamed moto-fastboot to just fastboot on my PC.) The blurry bits are where YOUR unique ID shows/is entered.
{
"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"
}
Root:
A moto-fastboot flashable /system image with su already in /system/bin (pre-reooted) This is based of the system in Yay4jugg's thread (NB: you need to be unlocked to flash this .)
Instructions:
0) Make sure your phone is charged.
1) Boot your phone in to fastboot mode, connected to PC.
2) At the prompt/cmdline type moto-fastboot flash system system.img
3) Make sure you have superuser app installed from market.
4) Enjoy!
CWM:
Romracer's official CWM thread for Photon
Calkculin's CWM thread
A video guide on how to root and install CWM for unlocked Bootloaders by qbking77
Kernels:
Hewett Kernel
Shabby's OC kernel
Problems?:
1) Don't panic.
2) Stop panicing.
3). If you get the following error messages, try restarting the flash process from the start:
- The "secure_motorola_flash" interface could not be found the super-file is secure and for re-flash, the phone needs a super-file that is not secure and for reflash. (0x7066)
4) Just try and go through with the unlock process anyhow
5) Try a different USB port, this is most likely because windows will reinstall all the drivers.
6) Try a different version of RSD Lite.
7) Make sure you put your phone in to USB NONE before plugging it back in. If you do not do this your system will not install all the devices correctly. Alternately, try Motorola Phone Portal mode.
8) Last resort PM me with very specific information about your problem and if applicable screen shots from your computer or phone.
Big thanks to Yay4juggs and Edgan.
The attached file below is only for Electrify owners and is untested
MOD EDIT: Attachment Removed
Yea BL unlock and root without dock? I gotta sleep, hope christmas comes in the morning!! I get some cash soon, gonna buy you guys a round! Man you guys are persisting and pushing tonight...
-DJ
Grats to everyone involved. You did amazing work.
Sent from my MB855 using XDA App
My stomach is ready. Thanks for the efforts and the work into this, we are grateful.
Chocolate pudding.
Has anyone tried this?
Sent from my MB855 using XDA App
evonate said:
Has anyone tried this?
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
I beleive its still being tested isnt it?
Hey you,
My name is Rick, and I am never gonna give you up. All of you have let me down, made me cry, and spent all day telling lies and hurting people. Your heart's been aching but you're too shy to say it. Honestly, have any of you ever gotten this from any other guy? I mean, I guess it's fun knowing the game and playing it, but you all take to a whole new level. Inside we both know what's been going on.
Don't be a stranger to love. You know the rules and so do I. I'm pretty much perfect. I have been nominated for a Grammy, and had a #1 hit. What games do you play, other than "running around deserting people"? And if you ask me how I’m feeling, I also have a banging hot girlfriend (We’ve known each other for SO long). I just wanted to tell you how I was feeling. I gotta make you understand.
Sent from my MB855 using XDA Premium App
newalker91 said:
When this is official, make sure to post this thread about 50 times in the Evo4G/3D sections. They've been talking trash since day one about this phone because the bootloader is locked.
Click to expand...
Click to collapse
theres a handful of people that actually knew anything about the photon and motorolas in general. i knew it wouldnt take long....im selling my nexus s as we speak, im that confident we will see awesomeness very soon.
newalker91 said:
When this is official, make sure to post this thread about 50 times in the Evo4G/3D sections. They've been talking trash since day one about this phone because the bootloader is locked.
Click to expand...
Click to collapse
I'll leave that up to you I don't own a Photon or Evo.
I was feeling good about 20 min ago. I have root (dock method) and started to get off the high that created figuring that it would be a while before somone unlocked the bootloader.......AHhhhhhh. Im gonna be checking this damn thread all night.......LMAO
ooxcfhxoo said:
I was feeling good about 20 min ago. I have root (dock method) and started to get off the high that created figuring that it would be a while before somone unlocked the bootloader.......AHhhhhhh. Im gonna be checking this damn thread all night.......LMAO
Click to expand...
Click to collapse
it is very exciting. i saw this right here and sold my nexus s this is my Photon in the picture btw...
Huge thanks to the2dcour for making this happen!!!!
what are the chances of getting the sbf tonight from someone?
ooxcfhxoo said:
what are the chances of getting the sbf tonight from someone?
Click to expand...
Click to collapse
0% check back tomorrow around noon EST.
I was thinking along the lines of a small (coffee sized) donation?....on say..........Newbury Street
ooxcfhxoo said:
I was thinking along the lines of a small (coffee sized) donation?
Click to expand...
Click to collapse
I _never_ ask for donations so don't feel obligated to, the work I do is a lot less intensive and technical than people imagine. As I've said before 99% credit belongs to moto for making this, 0.5% to the leaks/people who provide the leaks, and I'm happy to take the last 0.5% credit for being the script kiddie that assembles the pudding.
Before the files are posted for the public to download, we need to make sure that there are no side effects from this. Yay4Juggs and the rest of the testers should take their time and check to see if anything else was affected. Maybe if there was a ROM or 2 that they could test to see that it works that would be great.
I am already excited today to find out about dockless rooting but if the unlocked bootloader can be released, that would be a double whammie weekend.
ericdabbs said:
Before the files are posted for the public to download, we need to make sure that there are no side effects from this. Yay4Juggs and the rest of the testers should take their time and check to see if anything else was affected. Maybe if there was a ROM or 2 that they could test to see that it works that would be great.
I am already excited today to find out about dockless rooting but if the unlocked bootloader can be released, that would be a double whammie weekend.
Click to expand...
Click to collapse
That's precisely the reason that it hasn't been posted yet. There still may be side effects in the future as we are seeing with the atrix. Be warned, the unlock is irreversible and you should be careful. Most people will not need an unlocked bootloader. When you get custom kernels and CM that is another matter. People who dev this stuff can certainly use the unlock wisely. Till there is a reason for you to unlock I wouldn't bother unless you are adventurous and have a spare phone 99% of the reason people need / want unlock is for a custom kernel the other 1% is for using fastboot or non-bootstrap cwm. Hopefully you will have a non-bootstrap CWM soon. I'm rambling so I'll stop talking.
Im waiting and could care less if it bricked my phone......I'll recover from it. I'm prepared.
I would be using ......fastboot or a non-bootstrap cwm (when one is available).
i understand CWM is possible now and the reason for me unlocking my boot-loader is to get it done before someone puts the brakes on it.
I like to have access to the things i own based on principal. Its the same reason why i refuse to pay twice for the same data stream i already pay for in order to tether.
ooxcfhxoo said:
Im waiting and could care less if it bricked my phone......I'll recover from it. I'm prepared.
Click to expand...
Click to collapse
Coming tomorrow, I promise.
Related
Hello guys! At last, it is here! This tool has some distinct similarities with hasoon2000's tool (which is awesome by the way), but it also has few differences, more will be explained below.
Please note, this tool has certain requirements that you MUST follow!
This will flash a T-Mobile OTA, so if you are on ANY other carrier, you must have SuperCID, or wait for a similar tool that I may release in the future for your specific carrier. As of now, you must have SuperCID in order to run this tool (although you can try without, but results are NOT guaranteed)
As noted in the title, this tool is currently in beta, so use this as your own risk! I have tested this many times myself, but unfortunately, I haven't had enough testers respond to my request, so I am releasing this to the community as I know this would be a valuable tool.
Also, due to some people in this forum, I feel compelled to state this in big, bold, colored text.
This tool is only meant FOR S-Off users, and it does not, in ANY way, give you S-Off! NO, it will NOT work with an unlocked bootloader. To use this tool, you MUST have S-Off, plain and simple.
Click to expand...
Click to collapse
And now an explanation on what this tool does:
I've made a simple tool that will completely update your phone to the latest T-Mobile's OTA (Ice Cream Sandwich version), but without the need of reinstalling your custom recovery and reflashing SuperUser.
This is great for:
- People (especially newbies) with S-OFF that want to update to the latest OTA update, without having to find an Engineering/J-Bear hboot, without having to find a recovery to flash, without having to figure out how to flash superuser package, and without figuring out which fastboot commands to input.
- People without a SDCard, as this tool DOES NOT require a SDCard to flash the OTA!
- People who are stuck in a seemingly endless bootloop, and cannot figure out what to do in order to get the device back into a working state.
The true beauty of this tool is that it is ridiculously simple. All you really need to do is read the instructions, plug in your phone, run the program. In this program, you literally only have to touch your computer twice. The first one to accept the disclaimer, and then the 2nd to ensure that you have plugged in your USB cable.
Then this program will do the rest. It'll automatically detect which state your phone is in and then run the correct commands, check your S-Off state, flash the entire modified OTA*, detect whether the flash succeeded or failed, flash SuperUser and the free 4EXT recovery application, and does some other commands to ensure the phone works upon boot-up. This entire update should take no more than 15 minutes to complete, depending on your phone.
* The modified OTA update consists of 4Ext recovery, J-Bear Hboot (.2222), and a custom splash screen (hope you like it :laugh: )
Click to expand...
Click to collapse
Credits:
-MadMaxx82 for permission to use his awesome recovery and his free 4EXT recovery app
-Hyuh (and the entire unlimited.io team) for their work with S-Off and permission to use the J-Bear Hboot
-Hasoon2000 and Dark Nightmare for some of his suggestions and ideas
-Kgs1992 for some of his help on batch files
-Dark Nightmare, gregma, andy55, and shekki for testing this tool out
-I probably forgot some others, contact me if I did so I can credit you accordingly!
Click to expand...
Click to collapse
Before we go any further about this S-Off tool, you need to understand that there is always a risk of damaging your phone, even though I have personally tested this tool many times.
By downloading this tool, you accept all risks associated with this tool. I am not responsible if this breaks your phone, bricks it, or otherwise render your phone unusable. The standard disclaimer applies to this situation. Although I will try to help you, you are still responsible for whatever happens to your device.
Alright, moving on.
You MUST ensure that you have met the following requirements:
-The HTC Amaze 4G must have S-OFF
-The device must have SuperCID! (If it's a non T-Mobile phone)
-The device must be rooted!
-Battery must be *FULLY* charged
-A Windows computer with ADB/Fastboot drivers installed Files are included - but if it does not work, install these yourselves manually
-You must have an USB *DATA* cable. -- If you can transfer files and send adb/fastboot commands with the USB cable, it will work
-You must have USB Debugging turned on!
-Most importantly, you must have the ABILITY to follow directions
I cannot stress this enough. Make sure your battery is of decent charge. You do not want to have your phone shut down in middle of the process.
Click to expand...
Click to collapse
Instructions:
(READ THROUGH THE INSTRUCTIONS BEFORE DOING ANYTHING!)
Step 0) Ensure that your requirements are met.
Step 1) Make a nandroid backup if you want to restore your phone to the way it was before the tool. After backing up, make sure to make a backup of the nandroid backup, and both of the internal and external SDCards to your computer. I can not guarantee if the tool will wipe your external SDCard (It shouldn't, but it doesn't hurt to be safe)
Step 2) Disable any antivirus applications. This is a precautionary measure. You don't want the antivirus to remove something important in the middle of the update.
Step 3) Download the tool
Step 4) Verify the MD5 checksums to make sure they match. You do not want a corrupted tool.
The MD5 checksum is displayed on the download site, but if you need it, the MD5 checksum is:
f697211a9a49b293c4b99eee80de47d9
Step 5) After verification, use your favorite file extraction utility, put the entire ToolV2 folder (not just the files, but the entire folder) in an accessible location such as the C:\ Drive, Desktop, or whatever is the easiest for you.
Step 6) Open the folder *IMPORTANT* DO NOT change the files, move them, rename them, or anything of that nature. If you do, the tool most likely will not work.
Step 7) Open the RUN-ME.exe file (with an icon 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"
}
) *IMPORTANT* Do not extract the file named 'UltimateUpdater', leave it alone!
Step 8) Ensure that your phone is turned on. It can be in recovery, fastboot, or even in normal mode. It will automatically detect the device state. However, if possible, it is recommended to have your phone be booted into android.
Plug in the data cable. Make sure it is set to charge only (If booted into android). Do not forget to turn on USB Debugging!!!
Step 9) Follow on screen instructions. The process may take a while. Do not touch the phone, touch your computer, close the program, and most importantly, do NOT unplug the USB cable! It should auto-detect your device state, and it will detect your S-OFF state as a precautionary measure. When you get to this point like in the screen shot:
Follow it! Do not do any of those things! Leave it alone for 10 minutes! It will then detect if the update was successful. (If it does not do anything after 10 minutes, or does not detect anything, post on this thread and we'll see what needs to be done)
Click to expand...
Click to collapse
DOWNLOAD LINK
PLEASE READ BEFORE DOWNLOADING!
http://d-h.st/r22
Click to expand...
Click to collapse
Also, if you don't like the splash screen, this is your first step in figuring out how to mod your phone. Remember, DON'T post a question on how to change the splash screen, there ARE posts in the Amaze forums complete with step-by-step instructions on how to install a different splash screen!
It's time you started using the search button, my friend
Also, don't forget to press the THANKS button if this tool helped you!
Congrats! You finally released it! lol
hasoon2000 said:
Congrats! You finally released it! lol
Click to expand...
Click to collapse
Indeed I did! You know, you should test it out too. It's pretty neat if I say so
I gave ideas too , Jk JK, congrats on your release and thanks for the creds. :good:
Dark Nightmare said:
I gave ideas too , Jk JK, congrats on your release and thanks for the creds. :good:
Click to expand...
Click to collapse
Indeed you did! Maybe you'd like to read the credits again
Keylogger_0 said:
Indeed you did! Maybe you'd like to read the credits again
Click to expand...
Click to collapse
Lol I was jk dude, thanks though, appreciate it . Now back on topic, I'll be recommending this as the restoration option for all s-off users.:good:
Edit: Don't mention it bro, you did a good job and this will be a saviour for many.
Dark Nightmare said:
Lol I was jk dude, thanks though, appreciate it . Now back on topic, I'll be recommending this as the restoration option for all s-off users.:good:
Click to expand...
Click to collapse
Thanks!
thank you!!!
As I lost hope this utility actually worked!!! Hassons utility wouldn't read my phone. I flashed nightmare sense 1.6 and my phone wouldn't boot up, then I went to recovery like you're supposed to right? Using twrp and it just crashed and it automatically boot it up to the boot loop. And this helped so much thank you for this.
HTC amaze bootloop
Keylogger_0 said:
Hello guys! At last, it is here! This tool has some distinct similarities with hasoon2000's tool (which is awesome by the way), but it also has few differences, more will be explained below.
Please note, this tool has certain requirements that you MUST follow!
This will flash a T-Mobile OTA, so if you are on ANY other carrier, you must have SuperCID, or wait for a similar tool that I may release in the future for your specific carrier. As of now, you must have SuperCID in order to run this tool (although you can try without, but results are NOT guaranteed)
As noted in the title, this tool is currently in beta, so use this as your own risk! I have tested this many times myself, but unfortunately, I haven't had enough testers respond to my request, so I am releasing this to the community as I know this would be a valuable tool.
And now an explanation on what this tool does:
I've made a simple tool that will completely update your phone to the latest T-Mobile's OTA (Ice Cream Sandwich version), but without the need of reinstalling your custom recovery and reflashing SuperUser.
This is great for:
- People (especially newbies) with S-OFF that want to update to the latest OTA update, without having to find an Engineering/J-Bear hboot, without having to find a recovery to flash, without having to figure out how to flash superuser package, and without figuring out which fastboot commands to input.
- People without a SDCard, as this tool DOES NOT require a SDCard to flash the OTA!
- People who are stuck in a seemingly endless bootloop, and cannot figure out what to do in order to get the device back into a working state.
Before we go any further about this S-Off tool, you need to understand that there is always a risk of damaging your phone, even though I have personally tested this tool many times.
By downloading this tool, you accept all risks associated with this tool. I am not responsible if this breaks your phone, bricks it, or otherwise render your phone unusable. The standard disclaimer applies to this situation. Although I will try to help you, you are still responsible for whatever happens to your device.
Instructions:
(READ THROUGH THE INSTRUCTIONS BEFORE DOING ANYTHING!)
Also, if you don't like the splash screen, this is your first step in figuring out how to mod your phone. Remember, DON'T post a question on how to change the splash screen, there ARE posts in the Amaze forums complete with step-by-step instructions on how to install a different splash screen!
It's time you started using the search button, my friend
Also, don't forget to press the THANKS button if this tool helped you!
Click to expand...
Click to collapse
Hi, i flashed this OTA but my HTC amaze still in a bootloop, could you help me with this?
Are you on tmobile? if not did you SuperCID?
This tool has helped me several times, you should not be in a bootloop if you followed the steps correctly. it installs a completely new everything, recovery included (4ext). you should at least be able to access that from bootloader and restore a backup.
Andy1886 said:
Hi, i flashed this OTA but my HTC amaze still in a bootloop, could you help me with this?
Click to expand...
Click to collapse
What carrier are you on? CID? Can you also PM me your UpdateLog.log file found in the AIO folder of this tool? Don't post it here, PM it to me.
Gonna try it now... Will update u in a while..
This is the error I get while I am on trying to run the exe file...
I am running Win 7 ultimate X86 (32 bit)
vikasraj said:
Gonna try it now... Will update u in a while..
This is the error I get while I am on trying to run the exe file...
I am running Win 7 ultimate X86 (32 bit)
Click to expand...
Click to collapse
Any help regarding the tool from the developer..
First off...Thanks to Lokifish for all your hard work. I would post this in your thread, but I'm too new to post in the developer forums (though at least I was able to hit the thanks button).
So after reading through the entire deblur thread, being the n00b that I am, I was still hesitant to try it due to my uninformed decision to install the OTA update and not being able to find any post confirming it worked (on a stock phone) after that update. Well, I tried it anyway and just wanted to post somewhere that it worked flawlessly. I also wanted to include my own little "side guide" with precautions I took (after reading through the thread) that weren't in Loki's original guide, in hopes that it may help other n00bs such as myself to feel more comfortable with the process:
Make sure you have the latest drivers installed on you PC for your photon and the correct architecture. <--If you don't know what this means, stop here.
1. Root phone using photon torpedo method. http://www.groovypost.com/howto/motorola-photon-4-g-how-to-root-your-phone/ <--Thanks to kbeatzzz for his post. This method works and is easy to follow/do. <--Also thanks to edgan, obviously, for the photon torpedo method.
2. Install custom bootstrap recovery. <-- Thanks to topolovich for his post in the deblur thread.
This can easily be accomplished by following the "Custom Bootstrap Recovery" how-to video here: http://forum.xda-developers.com/showthread.php?p=17302907 <-- Thanks to qbking77 for these guides! Awesome work.
I think it's best to copy the apk to external sd, but you can copy to internal storage if you want, and just recopy it later.
3. Boot into the custom bootstrap recovery and make a backup to your external sd card.
4. After backup is complete and you rebooted your phone, power off and remove the sd card.
5. Reset to factory defaults <--from Lokifish Marz guide (Don't worry, this will not "unroot" your phone)
6. Install Superuser (by ChainsDD) from android market ...Needed for superuser permissions later, you don't have to do anything other than click allow when superuser asks if the apps can have permissions and make sure that the box is checked so superuser remembers the answer (that's important). Also be sure to update to latest binary from within superuser app.
7. Install BusyBox (by Stephen Stericson) from the market <-- thanks to Lokifish Marz, KyleIsTheBeast, NukeFish posts. This only installs the installer. You have to open it and then click install to actually get busybox installed. Don't mess with any of the settings!!!!
8. Copy the entire "1deblur_lite" folder over to internal storage (latest version) as per Lokifish Marz instructions in the OP of the Deblur Thread
(If you can't figure out how to get to the actual download link, see Post 3 of this thread for more details)
9. Power down and insert sd card, then power up and reinstall the apk for the bootstrap recovery. Make sure to go through all the steps again outlined in the video guide I mentioned earlier. If you copied the apk to your internal storage earlier, you'll have to recopy it, otherwise just install from sd card.
10. After rebooting from bootstrap recovery, unplug the charger, and uninstall any apps that are not included in this guide. (Many of them only allow you to uninstall updates, these apps will be there no matter what so no need to uninstall updates on these) Doing this step was something I added just to make sure there's nothing that will conflict with the script.
11. Turn on Airplane mode <--Thanks to Lokifish Marz suggestion and to ZeroManArmy for experiencing a problem and posting instead of giving up
12. Do not perform this step until you read step 13 and make sure charger is unplugged... Run the script as per instructions outlined by Lokifish Marz in the Deblur thread. Watch the video!
13. WAIT about 5 minutes before removing the battery. <--Thanks to ZeroManArmy for his post
14. Then reinsert battery and power up. You should now have a deblurred phone
If you softbrick the phone, you should be able to boot to the custom bootstrap recovery and restore your backup. (I can't guarantee this because I did not brick my phone, but the recovery mode continues to function normally after running the script) I did run into one little bug where the ringer toggle icon disappears after a while. This is likely an issue with one or more apps I have installed, because I haven't found any posts about this. I will ask in the Q&A forum to see if Lokifish might see it and help me get the icon back. This is a very minor issue though as the toggle still works.
I hope Lokifish does not take offense to the above guide. I just figured since taking these steps helped me to be "brave" and try it, they might help others too.
copy what?
umm on the http://forum.xda-developers.com/showthread.php?t=1575259&highlight=deblur fourm what am i suspose to copy to where
Silverdre said:
umm on the http://forum.xda-developers.com/showthread.php?t=1575259&highlight=deblur fourm what am i suspose to copy to where
Click to expand...
Click to collapse
In the OP of that link, scroll down to the video. Just above the video is a "Downloads:" link. That will take you to the Martian Imperium site. Click Enter. Click Downloads, click Motorola, click the link on the right (v1.0.8). From there you have to do a bit of add dodging (This helps Lokifish host the file and keep track of how many times it's downloaded):
DO NOT click any of the colored stuff, scroll down an click the ACTUAL BUTTON that says "Download or Watch". The new page will have a BIG GREEN ARROW pointing down in the center of the page. Click the "Download" link just below the arrow. Now you have to wait. Eventually it will connect and you can download the zip file. What you need to copy is located in that zip file: The "1deblur_lite" folder.
Note: You're probably going to have to close a bunch of popups. No worries, there's no adware/spyware or anything, just don't click anything you're not supposed to
Hey you have anyidea how to undo this deblur cause I tried asking loki and no reply
Sent from my MB855 using xda app-developers app
Silverdre said:
Hey you have anyidea how to undo this deblur cause I tried asking loki and no reply
Click to expand...
Click to collapse
Did you make a backup first as described in step 3 above? If so, boot into bootstrap recovery and restore from backup. Otherwise, you'll have to flash back to stock or another ROM. If you're on the 2.3.5 OTA update, which I suspect you are, then see below:
You can flash back to stock using a bootstrap flashable zip of the OTA update located here, thanks to mof9336
You can also flash to a De-Blurred Slim ROM that is bootstrap flashable and works with the 2.3.5 kernel/bootloader, also thanks to mof9336. You can find it here
I'm currently using v1 of the above ROM because I ran into some issues with voicemail on v2, but this doesn't seem to be the case with others who are running it, so I would definitely recommend trying v2 first.
Hope this helps
Help please
Hi everyone, im looking for help.
Y succesfully deblured my photon, everything was fine. My wife accidentaly factory reset my phone and now i cant use the phone y gets stucked on the contacting network screen, is there a way to boot to bootstrap recovery to restore my backup ig the phone cant boot? help please
elmaiko said:
Hi everyone, im looking for help.
Y succesfully deblured my photon, everything was fine. My wife accidentaly factory reset my phone and now i cant use the phone y gets stucked on the contacting network screen, is there a way to boot to bootstrap recovery to restore my backup ig the phone cant boot? help please
Click to expand...
Click to collapse
As far as I know, wiping the data partition (factory reset) kills bootstrap recovery because it's not a true custom recovery. The only thing I can think of would be to use RSD Lite. Check out the following post and be prepared to do a lot of reading. http://forum.xda-developers.com/showthread.php?t=1798145
Also, there may actually be a full Photon 2.3.5 SBF available by now, though I haven't found one. You may wanna try looking. If you find it, let me know.
Hope this helps
Keep in mind, I'm still a n00b myself and I am offering suggestions based on limited knowledge.
p0wder2 said:
As far as I know, wiping the data partition (factory reset) kills bootstrap recovery because it's not a true custom recovery. The only thing I can think of would be to use RSD Lite. Check out the following post and be prepared to do a lot of reading. http://forum.xda-developers.com/showthread.php?t=1798145
Also, there may actually be a full Photon 2.3.5 SBF available by now, though I haven't found one. You may wanna try looking. If you find it, let me know.
Hope this helps
Keep in mind, I'm still a n00b myself and I am offering suggestions based on limited knowledge.
Click to expand...
Click to collapse
thanx a lot, i followed that guide and my phone is working again :good:
Glad I could be of assistance
Can't open /sdcard/Universal
I tried following the method mentioned in Loki's post however, i get an error saying -
Script was not run successfully.
Stderr:
sh: can't open /sdcard/Universal
Please help
everything went well and phone is more fluid, faster & responsive.
love the adw launcher and updated it immediately.
but somehow my music & gallery are not working any more
i just get a blank light blue screen like of moto blur.
any idea or suggestion what to do. do i need to get separate apps
for these two things. or remove or reinstall something???
auto downgrade to 2.3.4
i was using deblured ota 2.3.5 for two weeks now.
but i had not reset my mopho.
i felt like doing it today. through keys by android recovery.
after which i found my phone is still deblured and rooted
but android version shows 2.3.4
and system 45.3.7
how is it possible that my rom got downgraded. did it remove the ota
does it mean i can now attempt to unlock.
is it risky, its unbelievable.
please through some light.
Run this in terminal emulator if you're rooted
su
cat /sys/firmware/fuse/ReservedOdm
And post your output
Sent from my sunfire using xda premium
terminal emulator and system info
hoslayer13 said:
run this in terminal emulator if you're rooted
su
cat /sys/firmware/fuse/reservedodm
and post your output
sent from my sunfire using xda premium
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"
}
Sorry your system was reverted back but your still stuck on the 2.3.5 bud. Your bootloader is locked down still
http://forum.xda-developers.com/showthread.php?p=26014213
Sent from my sunfire using xda premium
See my post from below from Original Development section:
Snuzzo said:
Ok from my testing I have found a different way for the s-on flashers to enjoy flashing a new rom without using fastboot. It does involve using an unsecured ram-disk which current JB roms do not offer. Sense roms do however and it works very similar to the DNA/Flashimggui technique of flashing a boot inside the rom. I have a script made for it but need feedback on it:
1) Include the script in ram-disk or system/bin? If ram-disk, a symlink can happen to system/bin if needed. Also might be easier to implement if in ram-disk and won't have to change much to the rom building. This could be easier implemented into ram-disk it's separate in a device tree away from the rom source.
2) Use what boot from what directory? Was contemplating labelling a folder called sonromflash, that would contain a boot.img inside the folder called newboot.img. That is going to have to be a collective census/poll.
3) Implement a menu choice or just a straight confirm flash of boot? Build this up to allow multiple boot.img's on (see point 2). May be named as boot<romname><romversion>.img.
4) An idea or a feasible implementation? This could add yet another factor in an s-on user thinking he/she is soft-bricked, so implement or just keep it as an idea for the future if needed.
5) If it does get implemented, how many users would learn fastboot? We all know some users just dive right in and only read parts of instruction or details (I was one of them when I first got this device, but yet was acclaimated in command prompts/scripts/and some C knowledge). Alot of softbricks can be easily fixed if read instructions properly. This would just add a "link in the chain", refer to 4th point.
This is just part of what I have been working on over the past couple weeks and what I found from that time when working on an update for a kernel on a rom outside of xda of a name I will not mention. It works 110% if utilized properly(read point 5). Tested courtesy of a couple of my faithful users that like the security of s-on & great friends if I might add.
PS:Sorry for the long rambling
Click to expand...
Click to collapse
TL;DR
Found a way to change the current boot flashing for S-On users which could lead into something a little more "user friendly" but could lead to beleiving a softbrick occurred when all that was needed was to factory reset and flash the matching rom upon reboot. I do have another way to utilize which is using another original work by con247 (not modifying his work at all). Feedback is needed in this change.
Snuzzo said:
See my post from below from Original Development section:
TL;DR
Found a way to change the current boot flashing for S-On users which could lead into something a little more "user friendly" but could lead to beleiving a softbrick occurred when all that was needed was to factory reset and flash the matching rom upon reboot. I do have another way to utilize which is using another original work by con247 (not modifying his work at all). Feedback is needed in this change.
Click to expand...
Click to collapse
Seems like a good idea for the people who haven't taken the S-Off plunge. My Rezound is my backup phone which I may give to my sister but I think the rewards outweigh the risks in this case.
Snuzzo said:
See my post from below from Original Development section:
TL;DR
Found a way to change the current boot flashing for S-On users which could lead into something a little more "user friendly" but could lead to beleiving a softbrick occurred when all that was needed was to factory reset and flash the matching rom upon reboot. I do have another way to utilize which is using another original work by con247 (not modifying his work at all). Feedback is needed in this change.
Click to expand...
Click to collapse
Most, if not all of us have s-off'd because of not wanting do deal with flashing via fastboot. I understand that it doesn't take long to flash and the process is pretty painless, but I am rarely sitting in front of a PC when I flash. If we all had the ability to flash the boot.img while being s-on and mobile and still keep the security of being s-on, I think that would be a win/win for everybody involved. Your scripting genius continues to amaze me. As long as those who run this understand the process, I cant see a downside
Hey Snuzzo,
I think this a pretty good idea for those who are not s-off, as long as those few understand and can read instructions. As TheBr0ken stated " Your scripting genius continues to amaze me" says it all about what you have done with your scripting.
Thanks for everything.
1Raiders said:
Hey Snuzzo,
I think this a pretty good idea for those who are not s-off, as long as those few understand and can read instructions. As TheBr0ken stated " Your scripting genius continues to amaze me" says it all about what you have done with your scripting.
Thanks for everything.
Click to expand...
Click to collapse
I agree. The scripts you have are awesome. For those that don't have s off this would cure them of having to do much work. Really its not a lot to do but some are uncomfortable messing with the phone but want the same advantages. I know I was scared at first doing the paperclip thing with the rezound but it turned out a piece of cake. Bricking a phone is natural I think if you really can't follow directions you probably should be extra cautious when messing with these things. But still, it's rare among a well rooted and versed community.
I think it's a great idea. There are plenty of people that are still s-on and this would be a great added bonus to make it easier on them. I also would never have figured out how to do this.
Hats off u da man!!
Sent from my ConD3m3dPaC-man ADR6425LVW using xda app-developers app
This would definitely help alleviate the questions resulting from standard s-on flashing procedures.
What do you think about point 2? Any input there? External sdcard? Have it search the whole sdcard or only a particular directory?
Sent from my ADR6425LVW using Xparent ICS Tapatalk 2
Snuzzo said:
What do you think about point 2? Any input there? External sdcard? Have it search the whole sdcard or only a particular directory?
Sent from my ADR6425LVW using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Set it to a directory like recoveries do for backups. Would help keep it organized.
Sent from my ConD3m3dPaC-man ADR6425LVW using xda app-developers app
I just went through the learning curve and think this would be great. I think at some point you will still be forced to learn fast boot as I rooted right before the latest update and that upgrade just about convinced me to just go s-off.
But I am staying s-on and would like to fash roms without a pc or a lot of prep work done on a pc.
Sent from my Infected Rezound using xda app-developers app
As the tester who sent his phone into boot loops with it... I'm still a fan of the idea, I just didn't have a good concept of exactly what was going on. I haven't tried to switch off a sense rom yet, but so long as that option would still exist, I'm all for it.
Quick message regarding recovery flashing and s-on from my chatter thread on MikForums
kcirtap420 said:
Had to flash amon ra to get on rezone (ReZone Redux), so I decided to try this and it worked!
{
"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"
}
Sorry about that SU permission in the way.
Click to expand...
Click to collapse
Might be making this live sooner that i thought.
I think it's a great idea. I came from the Incredible which was a tremendous device to flash on because it was so easy and painless, the Rezound...well it sucks being s-on. I hate being tied to a PC to throw on a different ROM and now I have an SDK issue to iron out and it makes me hate flashing rom's because its too many steps/commands. I want Android to be open and easy to flash, not jump through hoop after hoop. If you could make this happen I would come back to the Rezound, I got fed up and went back to my iPhone4. I really miss the Incredible!
Hello All,
Looks like I got myself into a pickle with my DNA......
Right now the only two things I can access on the phone are the bootloader and CWM.
How I got here:
I went into CWM recovery and deleted/formatted everything (absolutely everything that could be deleted and/or formatted), thinking I could flash a radio/firmware upgrade, then the LiquidSmooth rom from adb/fastboot. Been a long time since I've worked with this phone and now all I got is the bootloader and CWM. Thought I could use adb to push the rom zip to the device, then go into recovery and flash it the right way, but when I go to fastboot on the device and use the push command in adb it tells me "error device not found".
Gonna stop right there and seek some advice. What's the best way to correct this mess?
Thanks ahead of time!
PS: Working with a DNA with an unlocked bootloader (S-ON), and it was running the stock rom before the first OTA update. I did make a backup file and save it to my PC before I did anything. But, now adb is suddenly not recognizing that the device is connected so I can't push any files to it.
http://forum.xda-developers.com/showthread.php?t=2632351
HTC DNA
LG Optimus G
d08speed3 said:
http://forum.xda-developers.com/showthread.php?t=2632351
HTC DNA
LG Optimus G
Click to expand...
Click to collapse
Not real sure how this will help me.
I cannot boot into Android, and at this point whenever I try to push files to the device via adb it gives me an error and says device not found.
Tried to sideload in recovery?
RLGL said:
Tried to sideload in recovery?
Click to expand...
Click to collapse
Hmmm, I have not. Wasn't familiar with the term until now.
Actually just tried it and thought I was out of the woods. LiquidSmooth started to install, then failed/aborted. Here is a screen shot if someone can tell me what they can make of it:
{
"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"
}
Hackenstein said:
Hmmm, I have not. Wasn't familiar with the term until now.
Actually just tried it and thought I was out of the woods. LiquidSmooth started to install, then failed/aborted. Here is a screen shot if someone can tell me what they can make of it:
Click to expand...
Click to collapse
The problem with that turned out to be an outdated version of CWM. I updated it, only to find my phone would not get recognized in recovery by adb. Found that with the upgrade I also needed a driver upgrade which I took care of (after I had installed TWRP to test as well, just stuck with TWRP). Was able to flash rom (and it sucks). Looking for another one now that is more of a stock (de-bloated with perks, etc).
When I'm done there, should I run firewater to achieve S-OFF so I can update the radio as well, or is there a better way?
No os installed!!! Need help asap!!!!please
I hope im posting in the correct forum (forgive me if im not i mean no disrespect) im new to this rooting thing and made a choice the other day to root my htc dna thats currently on kit kat 4.4.2. I started out with clockworkmod and didnt like that so i then flashed twrp. The reason i didnt want to continue with clockworkmod is because i notice that there was some storage issues going on, i went to my settings and located my storage and saw that the other field was reading that over 13gb was being used up. I couldnt find out what the 13gb was so i started researching and found out that clockworkmod might have been having some issues with duplicating the os therefore taking up too much space. So what i did was try to flash the twrp thinking that would work and the storage was still being taken, so i started researching again and found out that i would need to do a factory reset and start all over....well when i did some how i erased the os as well now im stuck on the htc screen or i have the option of booting up into twrp but thats it.... I downloaded what i thought was the right ruu but thats not working i keep getting error 158....please somebody help me!!!!!!
CHRIST STARZ said:
I hope im posting in the correct forum (forgive me if im not i mean no disrespect) im new to this rooting thing and made a choice the other day to root my htc dna thats currently on kit kat 4.4.2. I started out with clockworkmod and didnt like that so i then flashed twrp. The reason i didnt want to continue with clockworkmod is because i notice that there was some storage issues going on, i went to my settings and located my storage and saw that the other field was reading that over 13gb was being used up. I couldnt find out what the 13gb was so i started researching and found out that clockworkmod might have been having some issues with duplicating the os therefore taking up too much space. So what i did was try to flash the twrp thinking that would work and the storage was still being taken, so i started researching again and found out that i would need to do a factory reset and start all over....well when i did some how i erased the os as well now im stuck on the htc screen or i have the option of booting up into twrp but thats it.... I downloaded what i thought was the right ruu but thats not working i keep getting error 158....please somebody help me!!!!!!
Click to expand...
Click to collapse
There is a search feature to use for finding out how to recover from your mistakes.
Try searching for error 158.
Hackenstein said:
The problem with that turned out to be an outdated version of CWM. I updated it, only to find my phone would not get recognized in recovery by adb. Found that with the upgrade I also needed a driver upgrade which I took care of (after I had installed TWRP to test as well, just stuck with TWRP). Was able to flash rom (and it sucks). Looking for another one now that is more of a stock (de-bloated with perks, etc).
When I'm done there, should I run firewater to achieve S-OFF so I can update the radio as well, or is there a better way?
Click to expand...
Click to collapse
Just for future reference, if you care to allow the dev community to thrive.
Don't use terms like "it sucks".
Maybe..., I don't like it,....or, I didn't care for it,....or it's not what I wanted, or needed, etc,..
But to know little about Android, and then to say that someone elses hard work sucks, is what makes devs say forget it and stop providing their free services to the community.
Just thought I'd point that out.
You can think I suck for saying so, but I'm honestly just trying to help you and the community by letting you know what impact users comments can have on Devs motivation to provide these things in their free time, with nothing in return.
Take it or leave it. Hope you find what suits you.
santod040 said:
Just for future reference, if you care to allow the dev community to thrive.
Don't use terms like "it sucks".
Maybe..., I don't like it,....or, I didn't care for it,....or it's not what I wanted, or needed, etc,..
But to know little about Android, and then to say that someone elses hard work sucks, is what makes devs say forget it and stop providing their free services to the community.
Just thought I'd point that out.
You can think I suck for saying so, but I'm honestly just trying to help you and the community by letting you know what impact users comments can have on Devs motivation to provide these things in their free time, with nothing in return.
Take it or leave it. Hope you find what suits you.
Click to expand...
Click to collapse
Well Said, and on that note, DEVS - I do appreciate all info that I receive here, whether it's from searching/reading or when a question gets answered. Thanks for all you do!!!
tat
santod040 said:
Just for future reference, if you care to allow the dev community to thrive.
Don't use terms like "it sucks".
Maybe..., I don't like it,....or, I didn't care for it,....or it's not what I wanted, or needed, etc,..
But to know little about Android, and then to say that someone elses hard work sucks, is what makes devs say forget it and stop providing their free services to the community.
Just thought I'd point that out.
You can think I suck for saying so, but I'm honestly just trying to help you and the community by letting you know what impact users comments can have on Devs motivation to provide these things in their free time, with nothing in return.
Take it or leave it. Hope you find what suits you.
Click to expand...
Click to collapse
I really love the fact that so many came in to actually ANSWER my question(s) and give relevant info on the issues I was experiencing (heavy sarcasm obviously). Ironic that only when I took a jab at someone's work (out of frustration) that the thread became active with people only sounding off on that issue, still ignoring the original problems I brought to the table. Top notch support!!!!!!
With that out of the way, to santod040; please accept my apology. I said that out of complete frustration and it was totally unecessary. Contrary to the negative vibes that comment conveyed, I DO appreciate all the devs hard work and allow me to publicly thank you for that. It was bad night of troubleshooting for me as I've been out of the loop for quite sometime and was rusty in several areas. Adding to that was the complete lack of helpful info I was finding not only on this site but several others. Kept going in circles and getting no where.
It is extremely important I point out that out of five different ROM's I tried to install via sideload, your's is the ONLY one that actually worked and in the end, I went back to it as it allowed me to finally boot into Android and enable USB debugging and help get the S-OFF process started via Firewater. Conclusively, I was finally able to get the baseband upgraded and get the phone fully up to date. So, thank you, wholeheartedly, and I apologize again for letting my stress get the better of me that night. LiquidSmooth saved my ass.
Cheers, my friend, and thanks again.
I can help if your s-off
hackenstein said:
the problem with that turned out to be an outdated version of cwm. I updated it, only to find my phone would not get recognized in recovery by adb. Found that with the upgrade i also needed a driver upgrade which i took care of (after i had installed twrp to test as well, just stuck with twrp). Was able to flash rom (and it sucks). Looking for another one now that is more of a stock (de-bloated with perks, etc).
When i'm done there, should i run firewater to achieve s-off so i can update the radio as well, or is there a better way?
Click to expand...
Click to collapse
if your s-off i have a method that will help you .....have you switched to s-off?
Avoid and pass by a fool and a madman
Great effort! thank you very much.
can you update the boot extractor from your previous post? i don't understand how to change the code u said here. thanks
jaygan93 said:
can you update the boot extractor from your previous post? i don't understand how to change the code u said here. thanks
Click to expand...
Click to collapse
It seems that many suffered from the payload_dumper, including me, and I'm thinking of a new extractor, something like that it's a standalone executable, containing all needed runtime libraries inside it so you don't need to install python/vc++, based on latest android sources, automatically detects many things, could be used universally on any ota for any brand, any version, and if it can't, it shows an warning and needed info if possible, at least.
Big problems to do this is that android build environment doesn't support windows (linux or macOS only and I don't use them), I can't spend much time on this, some phones such as black shark uses different their own codes and hide/never reveal those... etc...., so it requires a huge effort/time and I'm just thinking....
However, I will update the extractor or build a new extractor in any ways better, even though it takes some time.
wga0 said:
It seems that many suffered from the payload_dumper, including me, and I'm thinking of a new extractor, something like that it's a standalone executable, containing all needed runtime libraries inside it so you don't need to install python/vc++, based on latest android sources, automatically detects many things, could be used universally on any ota for any brand, any version, and if it can't, it shows an warning and needed info if possible, at least.
Big problems to do this is that android build environment doesn't support windows (linux or macOS only and I don't use them), I can't spend much time on this, some phones such as black shark uses different their own codes and hide/never reveal those... etc...., so it requires a huge effort/time and I'm just thinking....
However, I will update the extractor or build a new extractor in any ways better, even though it takes some time.
Click to expand...
Click to collapse
Yeah, actually i found out there is some payload dumper without instal phyton or something else and just an exe to extract the full ota payload.bin like in this post https://forum.xda-developers.com/mi-a2/how-to/guide-install-payload-bin-twrp-t3865319 i did try to extract the full ota an it did extracted all the img like boot, vendor, system etc. but i'm not sure that the system.img extracted from this payload dumper is useable or faulty one, so i'm not dare to flash it. Btw, thanks for the response i appreciate it. i hope you can find the best solution for us too.
It will get an unlock when it produces the firmware in a complex way. When it will flash the system partition and get lock again when the system is booting.
This is not necessary.
jaygan93 said:
Yeah, actually i found out there is some payload dumper without instal phyton or something else and just an exe to extract the full ota payload.bin like in this post https://forum.xda-developers.com/mi-a2/how-to/guide-install-payload-bin-twrp-t3865319 i did try to extract the full ota an it did extracted all the img like boot, vendor, system etc. but i'm not sure that the system.img extracted from this payload dumper is useable or faulty one, so i'm not dare to flash it. Btw, thanks for the response i appreciate it. i hope you can find the best solution for us too.
Click to expand...
Click to collapse
I'd tried them also, and they also generated some images corrupted when using on Black shark ota. I tried almost payload_dumper I could find at internet, only one, payload_dumper-master for incremental has the needed operation for full payload, and no one worked for incremental.
MCT_ said:
It will get an unlock when it produces the firmware in a complex way. When it will flash the system partition and get lock again when the system is booting.
This is not necessary.
Click to expand...
Click to collapse
I can't understand your word exactly, but the system never do lock/unlock during update. And... why are you talking that here? It has nothing to do with 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"
}
com.blackshark.ota/com.blackshark.ota.ui.TestActivity
MCT_ said:
View attachment 5008907
com.blackshark.ota/com.blackshark.ota.ui.TestActivity
Click to expand...
Click to collapse
It seems that you're sending wrong letter to worng address... This thread is for image_extractor/payload_dumper
wga0 said:
It seems that you're sending wrong letter to worng address... This thread is for image_extractor/payload_dumper
Click to expand...
Click to collapse
I don't see any problems with it, other than checking the signature.
And I don't see any posts about how happy everyone is to use TWRP on their device.
MCT_ said:
I don't see any problems with it, other than checking the signature.
And I don't see any posts about how happy everyone is to use TWRP on their device.
Click to expand...
Click to collapse
then use it yourself and don't disturb others. This is not for TWRP, not for update as you did. No relation at all! If you want to help others, do it right way in right place. I will not answer you again sorry...
wga0 said:
then use it yourself and don't disturb others. This is not for TWRP, not for update as you did. No relation at all! If you want to help others, do it right way in right place. I will not answer you again sorry...
Click to expand...
Click to collapse
First you guys talked about how to break the integrity of the system, then began to flash twpr recovery, now take the topic to the section of how you are going to install the update despite the modems. All you are on is trying to install an update. You have disabled a lot of devices, but there is not a single img backup in the discussion topic to restore it. It feels like you're deliberately stalling.
MCT_ said:
First you guys talked about how to break the integrity of the system, then began to flash twpr recovery, now take the topic to the section of how you are going to install the update despite the modems. All you are on is trying to install an update. You have disabled a lot of devices, but there is not a single img backup in the discussion topic to restore it. It feels like you're deliberately stalling.
Click to expand...
Click to collapse
You are totally wrong. All of it. Where I say to use the TWRP?
It's you who ask how to flash it and you're wrong again because BS2 has no recovery partition. I disagree or ask extremely careful when need it for reasons many times in this forum. Search it. The other guys also never said 'flash'! It's only you who saying that and making problems. Your writings for fastboot is also wrong, you can see the difference between your wrings yourself. You can use any side of slot. Such as set_active or current_slot is only a environment variables used when boot. Your words about 'SELinux' or other thins also are all wrong from your misunderstanding.
Here're many people who can't update because they never receive the update OTA, can't receive any services because it never released officially at their country, already bricked because of those who don't know the things exactly (like you).... There're many people who needs help. My own is also still at MP4 and the distributer/reseller never think about update. It's even officially released version!!
All of this, such as analyzing the payload.bin, making images from them, and more.... is to help those people at least by SW method. Those people who can't get services can do these method to revive their phone, to cover their deficient hw/sw with other sw, if root is needed to do so, then rooting it in most safest way...
What am I doing this meaningless.... what a waste of time...
plz search all it again, and think it again. Plz don't screw up other people with wrong knowledge. See what other people ask us... even doing these things is short in time... I or other guys never need to do this. Just enjoy myself is more easy, pleasant. I start this because many people suffered from fakers, who ask money for a deficient rooting and many lost their important stock images, money, updates... warranty and times. Now you're doing that. read all those and plz stop the verbal diarrhea...
wga0 said:
You are totally wrong. All of it. Where I say to use the TWRP?
It's you who ask how to flash it and you're wrong again because BS2 has no recovery partition. I disagree or ask extremely careful when need it for reasons many times in this forum. Search it. The other guys also never said 'flash'! It's only you who saying that and making problems. Your writings for fastboot is also wrong, you can see the difference between your wrings yourself. You can use any side of slot. Such as set_active or current_slot is only a environment variables used when boot. Your words about 'SELinux' or other thins also are all wrong from your misunderstanding.
Here're many people who can't update because they never receive the update OTA, can't receive any services because it never released officially at their country, already bricked because of those who don't know the things exactly (like you).... There're many people who needs help. My own is also still at MP4 and the distributer/reseller never think about update. It's even officially released version!!
All of this, such as analyzing the payload.bin, making images from them, and more.... is to help those people at least by SW method. Those people who can't get services can do these method to revive their phone, to cover their deficient hw/sw with other sw, if root is needed to do so, then rooting it in most safest way...
What am I doing this meaningless.... what a waste of time...
plz search all it again, and think it again. Plz don't screw up other people with wrong knowledge. See what other people ask us... even doing these things is short in time... I or other guys never need to do this. Just enjoy myself is more easy, pleasant. I start this because many people suffered from fakers, who ask money for a deficient rooting and many lost their important stock images, money, updates... warranty and times. Now you're doing that. read all those and plz stop the verbal diarrhea...
Click to expand...
Click to collapse
This code is just a ".cmd " project and some draft entries from the "one-click" flashing engine using ADB.
wga0 said:
You are totally wrong. All of it. Where I say to use the TWRP?
It's you who ask how to flash it and you're wrong again because BS2 has no recovery partition. I disagree or ask extremely careful when need it for reasons many times in this forum. Search it. The other guys also never said 'flash'! It's only you who saying that and making problems. Your writings for fastboot is also wrong, you can see the difference between your wrings yourself. You can use any side of slot. Such as set_active or current_slot is only a environment variables used when boot. Your words about 'SELinux' or other thins also are all wrong from your misunderstanding.
Here're many people who can't update because they never receive the update OTA, can't receive any services because it never released officially at their country, already bricked because of those who don't know the things exactly (like you).... There're many people who needs help. My own is also still at MP4 and the distributer/reseller never think about update. It's even officially released version!!
All of this, such as analyzing the payload.bin, making images from them, and more.... is to help those people at least by SW method. Those people who can't get services can do these method to revive their phone, to cover their deficient hw/sw with other sw, if root is needed to do so, then rooting it in most safest way...
What am I doing this meaningless.... what a waste of time...
plz search all it again, and think it again. Plz don't screw up other people with wrong knowledge. See what other people ask us... even doing these things is short in time... I or other guys never need to do this. Just enjoy myself is more easy, pleasant. I start this because many people suffered from fakers, who ask money for a deficient rooting and many lost their important stock images, money, updates... warranty and times. Now you're doing that. read all those and plz stop the verbal diarrhea...
Click to expand...
Click to collapse
This guy seems to be high lol. he is actually accusing us of bricking his phone and many others deliberately. I never said flash TWRP but I guess he doesn't know the difference between flashing TWRP and booting it.
Anyways, just ignore him he is talking meaningless and talk about non related things in different threads.
KM7 said:
This guy seems to be high lol. he is actually accusing us of bricking his phone and many others deliberately. I never said flash TWRP but I guess he doesn't know the difference between flashing TWRP and booting it.
Anyways, just ignore him he is talking meaningless and talk about non related things in different threads.
Click to expand...
Click to collapse
When you get root, via /data/media/... there is a dependency of the partition with internal storage, but you do not mention this and suggest using flash in its various variations. :good:
I don't even have a development section:
My bootloader is closed, I'm waiting for an update.
I've tried everything here, from bs2pro firmware on bs2 to payload_dumper and update.
With Google's floating code, this won't work, or you'll end up in the stone age.
Code is constantly moving.
You must obtain superuser rights legally, via the server.
Why do you need ROOT if you don't have a BootLoader, Recovery and ROM ?
What would delete installation APKs from system/app without disabling services ?
You made a copy of the system in img format for two months, with ROOT license on Board.
wga0 said:
EDIT: I found that more images in the full Android 10 OTA are corrupted when extracted with the payload_dumper, even including the boot image and modem.img, which is critically related to boot. I write this urgently... and will update soon... (Plz use with REPLACE part, or with below modified code)
Please be careful when you use the payload_dumper for full payload.
I found the payload_dumper doesn't have all the operations needed. It supports only two operations, REPLACE_XZ(lzma compression), REPLACE_BZ(bz2 compression), but BlackShark full OTA requires REPLACE(no compression, bsdiff or other format) also, and it generates some images incorrectly. It doesn't show you an error or any sign of malfunction also.
It seems that using it for the boot image only is okay, but images such as vendor.img, system.img are not correctly generated and it can brick your phone.
You can use payload_dumper-master instead. It supports the REPLACE operation for full payload, although it requires the vc++14.0 to compile the bsdiff library. I think easy way is to copy the REPLACE part in payload_dumper-master to payload_dumper, and use that.
Or you can modify the boot_extractor I uploaded to extract all files. Just delete the search part (comparing partition name), then it will extract all images.
oh... you need to change one more part...
Code:
#SOURCE_BSDIFF for Black Shark
elif op.type == op.REPLACE:
if pat[:3] == b'BSD':
odata = bytes()
for ext in op.src_extents:
ofile.seek(ext.start_block*block_size)
odata += ofile.read(ext.num_blocks*block_size)
pat = bsdiff4.patch(odata,pat)
ndata = io.BytesIO(pat)
for ext in op.dst_extents:
nfile.seek(ext.start_block*block_size)
nfile.write( ndata.read(ext.num_blocks*block_size) )
This will work for all images, all OTA for other phones (universally), and for both full, incremental of course.
Click to expand...
Click to collapse
i wish i saw this before hard breaking my black shark 2 pro now it is stuck in EDL i bought it before 6 days and now i think i will throw it into the trash
abd96iq said:
i wish i saw this before hard breaking my black shark 2 pro now it is stuck in EDL i bought it before 6 days and now i think i will throw it into the trash
Click to expand...
Click to collapse
Salam bro, try to hold down volume down button + power button while you are in EDL mode "this might take upto 60 seconds". If this doesn’t work, then try holding volume down when your phone reboot. This should take you to fastboot, from there you can run my full restore Black Shark 2 Pro batch, which you can get it from here.
Hope this works for you, goodluck.
KM7 said:
Salam bro, try to hold down volume down button + power button while you are in EDL mode "this might take upto 60 seconds". If this doesn’t work, then try holding volume down when your phone reboot. This should take you to fastboot, from there you can run my full restore Black Shark 2 Pro batch, which you can get it from here.
Hope this works for you, goodluck.
Click to expand...
Click to collapse
I tried but unfortunately doesn't work bro
I have even contacted s-unlock team but to avail
I think i will throw it in trash .
I am really sad
Thank you bro