$5 Bitcoin Reward to whoever helps me get this done.
Yes, I have followed olli's guide and I cannot make sense of any of it. Half of the stuff I did was missing out of his odd job of a "tutorial", not to insult him as he has contributed but to somebody like me, who has no ****ing clue its frustrating to follow broken English and missing steps. Here is what I have done.
Preparation
I have downloaded adb-setup, ran the program as an administrator.
{
"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"
}
I have downloaded a .img recovery file from the cyanogen website, which is named;
cm-13.0-20161220-SNAPSHOT-ZNH5YAO3XJ-crackling-recovery
Click to expand...
Click to collapse
Finally, I have downloaded SuperSU named;
UPDATE-SuperSU-v2.46.zip
Click to expand...
Click to collapse
I am aware there is a guide that already exists, it just skips too much of the vital information I need. I am not stupid, I am a comprehensive, experienced user on both linux and windows. I dont want to **** this phone up, I have some bad experiences with iPhones back in the day.
I need either a 1 to 1 talk through via Skype or for somebody to post here a step by step (Including everything, what buttons to press, when to plug in the USB cable) just a simple, step by step guide that does not skip half of the things I need or require me to hunt **** down when it could just be listed in the OP...
I am fairly certain this will take no longer than 10 minutes, and I will send you a $5 bounty in Bitcoin. I will be online for the next 2 hours ready to do this, let me know if you want to help me out.
Jayke. said:
$5 Bitcoin Reward to whoever helps me get this done.
Yes, I have followed olli's guide and I cannot make sense of any of it. Half of the stuff I did was missing out of his odd job of a "tutorial", not to insult him as he has contributed but to somebody like me, who has no ****ing clue its frustrating to follow broken English and missing steps. Here is what I have done.
Preparation
I have downloaded adb-setup, ran the program as an administrator.
I have downloaded a .img recovery file from the cyanogen website, which is named;
Finally, I have downloaded SuperSU named;
I am aware there is a guide that already exists, it just skips too much of the vital information I need. I am not stupid, I am a comprehensive, experienced user on both linux and windows. I dont want to **** this phone up, I have some bad experiences with iPhones back in the day.
I need either a 1 to 1 talk through via Skype or for somebody to post here a step by step (Including everything, what buttons to press, when to plug in the USB cable) just a simple, step by step guide that does not skip half of the things I need or require me to hunt **** down when it could just be listed in the OP...
I am fairly certain this will take no longer than 10 minutes, and I will send you a $5 bounty in Bitcoin. I will be online for the next 2 hours ready to do this, let me know if you want to help me out.
Click to expand...
Click to collapse
The Official Recovery is here
https://dl.twrp.me/crackling/
You put your phone in bootloader mode
run fastboot devices -----make sure your phone is seen by fastboot
run fastboot flash recovery (name of twrp recover above).img -------------copy and paste works if you don't like typing
Place SuperSu.zip on the Phone, SD card or internal storage
Boot to recovery and navigate to SuperSu.zip and install it.
Hi @Jayke.
Which step are you stuck at?
Did you get the ADB interface to work? If not make sure that the debugging (adb) is enabled under Settings - Developer options.
Also just as robin0800 suggested get TWRP as your custom recovery so you can flash SuperSU from there. Also make sure to get the latest Super SU from http://www.supersu.com/download (the .zip-file that's flashable from recovery).
If you're still stuck just reply with a detailed explanation on which step you're stuck at and I'll try to help.
Just to say, SuperSU v2.79 didn't work for me on COS13. I used v2.78.
The 'official' SU is now available - for crackling you need the 64bit-arm:
https://download.lineageos.org/extras
[sorry - this is for 14.1]
Related
I have just got my "mytouch3g" and was wondering if there is a way to change the boot screen??? Step by step instructions would be nice...
theflash1011 said:
I have just got my "mytouch3g" and was wondering if there is a way to change the boot screen??? Step by step instructions would be nice...
Click to expand...
Click to collapse
1st step.... SEARCH
2nd step....READ
3rd step....READ
I assume you mean the initial splash screen that pops up when you startup the phone. I did this on my G1, which was used on AT&T until I just got a Rogers Magic yesterday.
w00t.
Information can be found here: (Dream forum)
http://forum.xda-developers.com/showpost.php?p=3010171&postcount=1
I've verified that it works, I now have a pretty bootsplash on my new Magic.
{
"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"
}
korndub said:
1st step.... SEARCH
2nd step....READ
3rd step....READ
Click to expand...
Click to collapse
These replies don't help anyone
MikLSP said:
These replies don't help anyone
Click to expand...
Click to collapse
It should. Tough luck if you can't figure it out from there.
I've been struggling with this for a few days and may give up due to the risk involved.
Basically, it all depends on what version of the device you have.
1. You need to root your phone.
2. Check this website: http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking
It has detailed information on how to edit your boot screen.
Issues arise if you have a perfect SPL, like I do. (which is most likely what you bought) With a perfect SPL you will need to follow Ra's 30 - 40 steps to creating a Gold card (which might brick your phone and super complex) and then install an engineering SPL. After you've installed the busted SPL you can then use fastboot to push a new boot screen you've created using tools found is several other threads in this forum.
To do just about anything with the boot screen you'll need an extra non-scan disk SD card, RA's engineers SPL, the boot screen image converter created by JesusFreak (http://forum.xda-developers.com/showthread.php?t=467064) and some other stuff. I'd recommend doing some homework. MT3G is a super pain in the ass in comparison to the G1.
You might want to keep an eye on the thread I started yesterday... which is basically what you are asking... except I've done a lot of reading. (http://forum.xda-developers.com/showthread.php?t=568434)
http://ostebaronen.dk/?p=124 gives a great detailed instruction PLUS a load of splash screens!you dont have to make them just use his tut
i have made a couple of orange ones myself!
bonesy said:
http://ostebaronen.dk/?p=124 gives a great detailed instruction PLUS a load of splash screens!you dont have to make them just use his tut
i have made a couple of orange ones myself!
Click to expand...
Click to collapse
Yeah, that wont work for his American MT3G.
it should do its only flashing the splash screen, not the android screen
"fastboot flash splash1 mysplash.xxx"
its very simple, u can change the bootsplash on the mt3g, but first you have to change the spl, the one that comes on it already ends in 0006, you have to change it to 2005 the same one from the g1, after that u can change it the same way with the g1 thru fastboot flashing....thats how i did mine and a few of my frineds mt3g...good luck
Follow my walkthrough here to get root access and the correct SPL on a bone stock MyTouch 3G from t-mobile so you can fastboot: http://alldroid.org/viewtopic.php?f=96&t=76
Then follow this thread on how to create and flash your new boot screen through fastboot: http://forum.xda-developers.com/showthread.php?t=555114
If you only just got 5 posts I really recommend you to help other people first and search this forum.
brandenk said:
Follow my walkthrough here to get root access and the correct SPL on a bone stock MyTouch 3G from t-mobile so you can fastboot: http://alldroid.org/viewtopic.php?f=96&t=76
Click to expand...
Click to collapse
I was reading through and my question that I have is if I am already loaded with cyans lates 4.2.5 and all But I do not have the engineering SPL could I load it like it stated in your posted link from alldroid just like a basic update.zip and still be ok.
can anyone tell me why my htc desire is stuck at this screen when i put in the battery?
-- 1 minute later --
well, i can't post a pic since not allowed to link until after 8 posts
it looks like a boot screen with 3 android dudes on the bottom.
any ideas?
Your stuck at the bootloader. Means that there is no boot.img. You've done something to it. Just flash a rom and it'll be fine. Don't forget to wipe data.
ok, thats positive news so far
the things is, i think its water damage but not much water at all really. just a bit from snowing while skiing.
the power and volume buttons do not seem to respond AND the ohone turns on by itself when i insert the battery.
is it still just a case of 'flash a ROM'? or is there more?
oh, and here is the image..... finally,
{
"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"
}
You don't have root or a custom recovery, correct? You just want to go back to the stock Froyo?
I think if the power buttons don't work it may be a bit of a problem selecting options in that menu, since the power button works as "select" in that menu.
I think you could boot to recovery using command prompt, but I am not 100% sure about that.
Also, are you rooted? Do you have a custom recovery installed?
What is 'Kali CM7 Apps2SD'? Is that just another name for S2E?
sonoftobit said:
What is 'Kali CM7 Apps2SD'? Is that just another name for S2E?
Click to expand...
Click to collapse
--- confusion ensues ---
my phone is NOT rooted NOR does it have anything custom.
i would simply like to go back to the original v2.2 that i had before this happened.
thanks for all suggestions and help
liquidmonkey said:
my phone is NOT rooted NOR does it have anything custom.
i would simply like to go back to the original v2.2 that i had before this happened.
thanks for all suggestions and help
Click to expand...
Click to collapse
Do you have a note of which rom was installed in your device? Is it carrier locked? Branded?
Select the newest RUU that fits your phone & carrier from http://shipped-roms.com/shipped/Bravo/. Extract the ROM, rename to PB99IMG.zip, place in root dir of sd-card and reboot. Should do everything else automatically.
don't really follow the whole ROM question?
my phone has android v2.2, is NOT branded, is NOT locked and NO rooting.
and i should add that i am sweden if that matters.
The file you download from shipped roms is an exe file. When you execute the file it will extract a couple of files to your harddrive. Among those is a file named ROM.zip. That's the one you're looking for.
When I extracted it the file was here C:\Users\*User Name*\AppData\Local\Temp\{722DC7D5-7B69-4EBC-B6FB-B63AE38C01DE}\{50F2F878-636A-496F-A7CB-544C067E0C4B}
The ROM on shipped ROMs are all the standard carriers version that are unmodified.
liquidmonkey said:
don't really follow the whole ROM question?
my phone has android v2.2, is NOT branded, is NOT locked and NO rooting.
Click to expand...
Click to collapse
Yeah but there are different versions of 2.2 depending on carriers etc, thats why I was asking!
I *think* any of the ROMS here with RUU at the beginning & WWE in the filename should work. (I am not 100% sure about this, as I have not had an official rom installed for AGES).
You will then have to follow sonoftobit's instructions I think, don't ask me how to extract the ROM though, as I don't know how to do it!
PS sonoftobit - Ignore this liquidmonkey!
If you go to the CM7 nightly thread and go to the 2nd post, Kali has a script for enabling Apps2SD. That is what I am running, tried to use S2E but it screwed things up royally and I had to restore a Nandroid!
Yeah, I had the same problems with S2E. I'm using DarkTremor App2SD now which has worked flawlessly ever since (both Sense Froyo and CM7). Also there's A2SDGUI for DarkTremor now which makes it even better.
StuMcBill said:
PS sonoftobit - Ignore this liquidmonkey!
Click to expand...
Click to collapse
why on earth would you write that?
so check it out!!!
i have had the phone off for a few more days and then put in the battery and BANG, it started up after a little while.
problem was that my battery only lasted 10 seconds so i was not able to fully test things.
then i put the battery in again and i was back where i started, crappy boot screen.
is there something in the phone that keeps memory of the boot screen and then disapates after a day which would explain why it started today.... or?
{
"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"
}
This a short list of frequently asked questions about the Samsung Galaxy Tab 3 8" (SM-T310) and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses.
Do not use this thread as a general helping thread.
Q1: How do I root my SM-T310?
First you're gonna need a custom recovery installed.
Download the following files to your computer: Odin, TWRP, Root
Extract Odin into a new folder and then TWRP in Odon's folder. After that's done start the Odin tool and put your device into download mode. To do this, power it off and hold the Home + Volume Down + Power buttons until you see the warning screen.
Once that's done, connect your device to your computer and wait till Odin recognizes it. If it doesn't usually an installation of Samsung Kies would fix it.
After the device is recognized sucessfully click on the PDA button in Odin and navigate to the TWRP file location and load it.
Wait for the PASS message and reboot your device. (Without disconnecting it)
Once done, boot into TWRP and hold your device in portrait mode, tap Reboot on the bottom right of the screen and then select System on the next menu.
Once you do this you will be asked to install root. If that doesn't work for your, copy the Root zip file to your SD Card, boot into TWRP and flash it as a normal zip.
Click to expand...
Click to collapse
Q2: How can I enter recovery?
To enter recovery, power off your device and hold Power + Volume Up buttons untill you see the Samsung Galaxy Tab 3 splash screen and let off the Power button untill it boots you into recovery.
Click to expand...
Click to collapse
Q3: Which is the best ROM/Kernel?
Honestly, there is no "best". It's all based on personal choice. For example; I may like heavily customizing my ROMs whereas you may like it to look at basic as possible. The best thing you can do is to just test out different ROMs/kernels/modems and see which you prefer.
Also, please don't ask which is the best because your post will be deleted as it's against forum rules.
Click to expand...
Click to collapse
Q4: Am I required to backup my data before flashing anything?
No you're not, but it is definitely a good idea, especially when flashing a ROM with an updated base, because if you don't do a backup and then something goes wrong, it means that you'll lose all your apps, data etc.
Click to expand...
Click to collapse
Q5: Does this device have a good battery life?
We all have different apps installed, use our phones for different amounts of time, have different ROMs and kernels installed etc. so we will all experience different results regarding battery life.
Click to expand...
Click to collapse
Q6: I'm not sure whether to get the Samsung Galaxy Tab 3 8"/what other tablets compare to the Tab 3 8"?
The only person who can make you want the device is you. If you're not sure whether to get this tablet, go to your local devices shop which has stock and have a test run of it for yourself. If you're not sure what device to get and want to compare between your choices, please use the following thread - Device Suggestion Thread
Click to expand...
Click to collapse
If you have any suggestions regarding this thread's content, feel free to post them.
+1 For this Mate. :thumbup:
This looks like a pretty hard nut to crack. I don't know exactly what caused it. I was rooted for a few days and was just reflashing Magisk (messing about you could say) when it turned up. Previously, I just had the warning with yellow text which is what everyone gets after unlocking the bootloader. So here goes the overview, please bear with me:
===> I reset the phone by flashing OnePlus5TOxygen_43_OTA_006_all_1712062242_69a5125fb2eb4d87.ZIP (OxgengenOS 4.7.4). <===
Exact steps on how I did that:
1) I flashed the stock recovery image via fastboot ( I got it from Oneplus's website)
2) I booted into the stock recovery I flashed in step 1 and flashed the entire ZIP (the one with the long name above). Probably flashed the recovery twice but yeah.
But no dice. It will absolutely not go away. The zip does not contain any other IMG's apart from boot.img and recovery.img so I can't really flash other partitions like system via fastboot. I CAN flash system via my nandroid backup, and I did, but that still did not help.
Here is the error I got. It's from a google search but it resembles the error on the OPO5T very nicely. So can the experts chime in please?
{
"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"
}
Not used to posting my own answer but maybe this will help someone. You need a full reflash with the Qualcomm tools. OPO support can do this, or anyone with the flashing tool, the correct firmware image, and drivers (the latter being easy to find).
There are tutorials online to do this, the only thing missing is the correct firmware image.
To summarise the requirements:
1) Qualcomm drivers (easy to find)
2) Qualcomm Flash tool MsmDownloadTool V4.0.exe (fairly easy to find)
3) The correct *.ops firmware image (hard to find and you need the password)
Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info
Bradl79 said:
Yeah we had been trying to crack the password with no success, hopefully someone will, thank u for the info
Click to expand...
Click to collapse
I can tell you its lenght if that helps? That should narrow down the amount of combinations. Unless its different per download link they send.
Yes please that would cut down a lot
Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.
If we already have the opt file someone could just set up a keylogger on their machine and have op support do the remote flash and thus capture the password from them lol
Bradl79 said:
Yes please that would cut down a lot
Click to expand...
Click to collapse
Jeroen1000 said:
For OnePlus 5T "OxygenOS 4.7.2-171116.zip" it is exactly 10 characters. The driver RAR-password is a lot longer (>20). Don't even try to brutefoce that.
Click to expand...
Click to collapse
Has any one had any luck with the password? I'm in the same soup as well!
randallstevens said:
Has any one had any luck with the password? I'm in the same soup as well!
Click to expand...
Click to collapse
still going... only on 4th character out of 10 been running for a couple days
Bradl79 said:
still going... only on 4th character out of 10 been running for a couple days
Click to expand...
Click to collapse
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.
randallstevens said:
Do you mean you have the first three? If so can you share or PM it? Not sure if you mean that brute forcing has reached only a permutation of 4 characters.
Click to expand...
Click to collapse
It is Bruteforcing meaning I started with 10 characters
1111111111
And it's still trying to decrypt, I am at something aroun
111111gw7&
So it's going one by one going through each character
Hello, my 17 year old got the new one plus 5t yesterday,
He rooted the phone but then realised he couldn’t use certain apps with it rooted, so he uninstalled magisk
He rebooted the phone but it only went into custom recovery and wouldn’t load an OS
Because that didn’t work, he tried flashing an OTA update.
Now his phone is stuck on an upside down screen and a fuzzy section on it.
I know ZERO about android phones.
Should I wait for the support to open at one plus? Or is there something I can do to fix 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"
}
brickedmum said:
Hello, my 17 year old got the new one plus 5t yesterday,
He rooted the phone but then realised he couldn’t use certain apps with it rooted, so he uninstalled magisk
He rebooted the phone but it only went into custom recovery and wouldn’t load an OS
Because that didn’t work, he tried flashing an OTA update.
Now his phone is stuck on an upside down screen and a fuzzy section on it.
I know ZERO about android phones.
Should I wait for the support to open at one plus? Or is there something I can do to fix this?
Click to expand...
Click to collapse
tell him to download this (full firmware)
https://otafsg.h2os.com/patch/amazo...xygen_43_OTA_011_all_1804241056_afd261322.zip
Boot to recovery, copy zip to internal storage, swipe to wipe and flash the zip.
p/s if it cannot boot to custom rec then use this guide
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Thanks so much for your reply,
In the end I spoke to one plus and they couldn’t fix it, they said I could exchange it free of charge, so he got a brand new phone yesterday! Thank god. I’m never letting him root it again tho, he only had it 24hours!!!
nguyenlucky said:
tell him to download this (full firmware)
https://otafsg.h2os.com/patch/amazo...xygen_43_OTA_011_all_1804241056_afd261322.zip
Boot to recovery, copy zip to internal storage, swipe to wipe and flash the zip.
p/s if it cannot boot to custom rec then use this guide
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Click to expand...
Click to collapse
brickedmum said:
Thanks so much for your reply,
In the end I spoke to one plus and they couldn’t fix it, they said I could exchange it free of charge, so he got a brand new phone yesterday! Thank god. I’m never letting him root it again tho, he only had it 24hours!!!
Click to expand...
Click to collapse
You should let him experiment again, this time with some more reading here on the forum before though. He can learn a great deal about how different systems are built and the working parts of them.
And mostly since it's really fun, these days its really hard, close to impossible to mess up the phone bad.
Yes - He should be allowed to root it again - He needs practice
fkofilee said:
Yes - He should be allowed to root it again - He needs practice
Click to expand...
Click to collapse
I'm also in that opinion. He should be allowed to root again.
I may have an idea why this happened: Instead of an Oneplus 5T Firmware, he may have flashed a Oneplus 5 Firmware..
you mentioned an upside down turned Screen... well, the normal oneplus 5 had their Display assembled upside down and oneplus thought it would Fixing it by turn the Display Output by 180° by Software configuration. Your son should be Aware of that Oneplus 5 and 5T are different devices.
First step is using fastboot adb tool to flash some custom recovery first such as twrp,then download the latest oxygen system from oneplus official website(should be about 1.6gb) flash it inside and reboot. U will get a official system with official recovery set everything up. Then flash the custom recovery again and flash custom kernals such as bluespark or franco. goto the google pay or other root blocked app to set up everything.
Now you can flash the magisk to get root and activate magisk hide immediately right after u reboot. Remenber to tick the apps you need to hide the root for.
Wish u success:good: