Hello,
is there a way to modify or get rid of the warning screen that pops up if you boot your unlocked XX?
You know, that one with the yellow triangle and the five seconds delay.
As I understand you can modify it with fastboot, but I only found that threads for some Motorola devices, so is it possible with the Xperia X?
Maybe by relocking the bootloader?
bauboni said:
Maybe by relocking the bootloader?
Click to expand...
Click to collapse
Well, I installed a custom kernel with root. If I relock the bootloader, I would lose root wouldn't I? So I think that's not an option for me ?
Anyone please? :/
ceejay105 said:
Anyone please? :/
Click to expand...
Click to collapse
Cant do it. That warning is in the bootloader, not the kernel so it can't be modified.
shoey63 said:
Cant do it. That warning is in the bootloader, not the kernel so it can't be modified.
Click to expand...
Click to collapse
Thanks for your answer. In the Motorola forums someone described to remove it by flashing a custom logo.bin file. Isn't there any way to adopt this for the XX?
ceejay105 said:
Thanks for your answer. In the Motorola forums someone described to remove it by flashing a custom logo.bin file. Isn't there any way to adopt this for the XX?
Click to expand...
Click to collapse
If there was a logo.bin in the kernel ramdisk it would be possible, but there isn't. The warning is embedded somewhere else in the bootloader partitions and attempting to modify those would most likely cause a hardbrick. I wouldn't recommend going there...
shoey63 said:
If there was a logo.bin in the kernel ramdisk it would be possible, but there isn't. The warning is embedded somewhere else in the bootloader partitions and attempting to modify those would most likely cause a hardbrick. I wouldn't recommend going there...
Click to expand...
Click to collapse
Okay, seems I have to stick with that warning though. Thank you anyway.
Well someone did find that the PNG format image itself is in \ramdisk\res\images\warning
I can confirm that it is not in the kernel. The kernel does contain two folders at this location with some battery images (likely when you charge while phoine is off) but none of them are named warning. I own X Compact myself. Just wanted to mention this if someone with the nessesary skills decides to take up this task.
RaXelliX said:
Well someone did find that the PNG format image itself is in \ramdisk\res\images\warning
I can confirm that it is not in the kernel. The kernel does contain two folders at this location with some battery images (likely when you charge while phoine is off) but none of them are named warning. I own X Compact myself. Just wanted to mention this if someone with the nessesary skills decides to take up this task.
Click to expand...
Click to collapse
I really don't know why someone would be so happy to remove that warning, but anyaway if someone has the time it would be nice
FoxTheLegend said:
I really don't know why someone would be so happy to remove that warning
Click to expand...
Click to collapse
Because it's unnecessarily annoying and jarring/alarming every single time your phone boots up?
Every single Motorola phone I've owned I've been able to overwrite the warning with a custom image with a simple and safe fastboot command. It ends up looking a lot cooler too than the stock (locked) screen since you can put whatever you want in there as long as it's the entire size.
The Motorola forums have entire threads dedicated to shared bootlogo images, with the only difference being the size/resolution, but otherwise they work cross-device.
Sorry....Had a Motorola Moto g2 once that i could Just sas: Okay flash this and this, BAM!" and it was removed.....but in Sony devices IT SEEMS it ist imbedded into bootloader
FoxTheLegend said:
I really don't know why someone would be so happy to remove that warning, but anyaway if someone has the time it would be nice
Click to expand...
Click to collapse
we would like to do that because
1. it is annoying
2. 5 seconds less boot time because of bootimage not even loading when it appears
Some random said:
we would like to do that because
1. it is annoying
2. 5 seconds less boot time because of bootimage not even loading when it appears
Click to expand...
Click to collapse
Yeah dude I got it but I wrote this thing like 2 years ago
FoxTheLegend said:
Yeah dude I got it but I wrote this thing like 2 years ago
Click to expand...
Click to collapse
I realised that too now.....
Related
So, yes - I need to know how to brick my phone beyond repair please....
"Why !?" I hear you ask....
Imagine the situation: Some b*st*rd has stolen your phone . You are never going to see it again... ever... absolutely zero chance of getting it back...
If you had the option to brick it so no one could sell or use it, would you?
Yes, of course you would!!
It's possible to remotely execute any BusyBox/Terminal Command using the application Tasker and I want to know which one would do the most damage!?
Please let me know! "How do I totally brick my phone?"
load a corrupted radio file
ohhh, sorry to hear that. I had the perfect solution if you still had the phone. But um yea I don't take out my phone near any friends. My brother got his vibrant stolen only after 2 weeks.
Didn't mean to mislead! My phone hasn't actually been stolen! But I'm working on security profiles and need to know what the final command should be to end its life....
Can you flash a radio from the Terminal Emulator?
Sent from my HTC Desire using XDA Premium App
This is what I did and I actually got Verizon to give me a re-furb. What it does is bring you to the htc inc white screen then nothing else. Use root explorer go into systems/fonts and change the name on one of the droidsans.ttf files. I think I totally erased the files but changing them should cause the phone to be totally [email protected]#$. I hope this messes up your phone. Lol
skinny jeans piss me off
BIGshot87 said:
This is what I did and I actually got Verizon to give me a re-furb. What it does is bring you to the htc inc white screen then nothing else. Use root explorer go into systems/fonts and change the name on one of the droidsans.ttf files. I think I totally erased the files but changing them should cause the phone to be totally [email protected]#$. I hope this messes up your phone. Lol
skinny jeans piss me off
Click to expand...
Click to collapse
Great, thank you! Shall test and hopefully be able to revert in fastboot?!
skinny jeans piss me off too...
Further to the above, does anyone know if it's possible to disable entering recovery by deleting certain system files?
brandall said:
Further to the above, does anyone know if it's possible to disable entering recovery by deleting certain system files?
Click to expand...
Click to collapse
Flash a stock recovery image to disable flashable recovery. Also renaming a file doesn't make the phone broken, it just doesn't allow it to boot.
Sent from my Hero that never dies! ;D
dastin1015 said:
Flash a stock recovery image to disable flashable recovery. Also renaming a file doesn't make the phone broken, it just doesn't allow it to boot.
Sent from my Hero that never dies! ;D
Click to expand...
Click to collapse
Thanks - I need it to boot - just don't want someone else to be able to wipe and/or flash a custom ROM
I need to read up if there's a way to flash a recovery image from the Terminal...
hmmm...
brandall said:
Thanks - I need it to boot - just don't want someone else to be able to wipe and/or flash a custom ROM
I need to read up if there's a way to flash a recovery image from the Terminal...
hmmm...
Click to expand...
Click to collapse
To flash a recovery image from TE use this if your ROM supports it: flash_image recovery /sdcard/(name of recovery)
An example for me is: flash_image recovery /sdcard/recovery-clockwork-2.5.0.7-heroc.img
Sent from my Hero that never dies! ;D
dastin1015 said:
To flash a recovery image from TE use this if your ROM supports it: flash_image recovery /sdcard/(name of recovery)
An example for me is: flash_image recovery /sdcard/recovery-clockwork-2.5.0.7-heroc.img
Sent from my Hero that never dies! ;D
Click to expand...
Click to collapse
That's brilliant thank you. Do you know if that can be reverted by flashing the custom recovery image again? Or will I lose the ability to do that once I flash back to stock?
Sorry for the questions, this stuff confuses me...
brandall said:
That's brilliant thank you. Do you know if that can be reverted by flashing the custom recovery image again? Or will I lose the ability to do that once I flash back to stock?
Sorry for the questions, this stuff confuses me...
Click to expand...
Click to collapse
As long as you're on a custom ROM that supports flash_image you can flash a recovery image through TE.
Sent from my Hero that never dies! ;D
dastin1015 said:
As long as you're on a custom ROM that supports flash_image you can flash a recovery image through TE.
Click to expand...
Click to collapse
Thanks again - mine does, so sorted
Never thought of using lookout?
Sent from my MB860 using XDA App
makr8100 said:
Never thought of using lookout?
Click to expand...
Click to collapse
Hopefully going way beyond that... see >>here<<
Do you have the information to know whether it's truly been stolen yet? I'd make sure that it's really been stolen and you, for sure, wouldn't get it back before attempting something like this. I definitely wouldn't want to brick my own phone on purpose just to find out I forgot it somewhere...
ChrisDang said:
Do you have the information to know whether it's truly been stolen yet? I'd make sure that it's really been stolen and you, for sure, wouldn't get it back before attempting something like this. I definitely wouldn't want to brick my own phone on purpose just to find out I forgot it somewhere...
Click to expand...
Click to collapse
See the link above Chris. My phone hasn't actually been stolen, but these commands will be a last resort feature of Sherlock Droid.
Agreed, it would be a nightmare to brick it and then find it under the sofa!
Sent from my HTC Desire using XDA Premium App
You shouldn't brick it quite the opposite, the thief should be able to keep using the phone as much as possible but in the mean time the gps should be secretly turned on and photos should be make so you can track the thief or if that fails publish his info and name and shame him
godutch said:
You shouldn't brick it quite the opposite, the thief should be able to keep using the phone as much as possible but in the mean time the gps should be secretly turned on and photos should be make so you can track the thief or if that fails publish his info and name and shame him
Click to expand...
Click to collapse
You are absolutely right godutch, that is the main aim of the profiles to keep booting into the OS at every opportunity, even using fake recovering images (as in a photo of the custom recovery screen) for the splash and boot animation that appear to be the device gathering system information - all the time it will actually be booting with the launcher, notification bar and lock screen etc disabled so not to give it away - once there the priority is to get a GPS fix
However, there will come a point when you've not heard a peep from the device in days and perhaps your insurance (if you have it) have already paid out... In which case, some users will want to execute the remote 'self destruct' command, to make sure the phone will never be usable to anyone else....
Edit: Trying to make the thief provide a valid gmail address and forwarding the new number if the SIM is changed are all in there too!
What if thief changes to SIM that has no data plan or does not enter any wifi area?
Title just has it...
What are fastboot files for? everyone keep saying it's a good thing and etc... but I don't really know what's the biga deal
It's the phone os in a file.
Different from the old .sbf, in that it doesn't destroy user settings, accounts, sms etc.
Shadowdancer123 said:
It's the phone os in a file.
Different from the old .sbf, in that it doesn't destroy user settings, accounts, sms etc.
Click to expand...
Click to collapse
To add to that it is for recovering from a soft brick. So it is kind of a big deal. It may also helps devs not be so gun shy.
inheme said:
Title just has it...
What are fastboot files for? everyone keep saying it's a good thing and etc... but I don't really know what's the biga deal
Click to expand...
Click to collapse
If u install a costum rom, fastboot files let you back to moto stock rom
Sent from my XT910 using Tapatalk
Thanks guys!
So is there any fastboot for the GSM version yet? If not, is there any way to extract it?
cheekrox said:
So is there any fastboot for the GSM version yet? If not, is there any way to extract it?
Click to expand...
Click to collapse
Spend about 2minutes and look at developer threads, you can find them
Sent from my RAZR using Tapatalk
Bit confused here; the boot loader is locked so you can't change the kernel (os). Is the fastboot stuff everything but the kernel; just the jvm; not the jvm but the basic files that are executed by the jvm; the ...???
jake21 said:
Bit confused here; the boot loader is locked so you can't change the kernel (os). Is the fastboot stuff everything but the kernel; just the jvm; not the jvm but the basic files that are executed by the jvm; the ...???
Click to expand...
Click to collapse
The kernel can be flashed by these files, since it's encrypted with the correct password.
We'd need that password to bypass the hardlock, but unfortunately noone will ever want to experiment with that since it may blow e-fuses, rendering his or her phone forever dead.
By the little I know of cryptography, the fastboot only has half the key.
Previously no phone actually used an e-fuse (it was proven on earlier moto phones that e-fuse was not enabled). Does the razr actually use an e-fuse ?
Shadowdancer123 said:
The kernel can be flashed by these files, since it's encrypted with the correct password.
We'd need that password to bypass the hardlock, but unfortunately noone will ever want to experiment with that since it may blow e-fuses, rendering his or her phone forever dead.
By the little I know of cryptography, the fastboot only has half the key.
Click to expand...
Click to collapse
Sprint Moto X [XT1056] Stock ROMS
By using any of these you agree that I am not responsible for ANYTHING that can or may happen to your phone
Click to expand...
Click to collapse
Like this guy said:
iKrYpToNiTe said:
Word to the wise if you don't know how to use RSDLite or Fastboot to restore your phone then leave this thread now please!
Click to expand...
Click to collapse
-----------------------------------------------------------------
KIT KAT 4.4.4
System Version: 212.44.28
Software update 08/2014
Code:
[B]DETAILED ENHANCEMENTS:[/B]
Android™ 4.4.4, KitKat® - Android 4.4.4, KitKat, is the latest release of the Android platform. This release includes several stability, framework and security fixes in addition to accuracy improvements to the power profile.
Camera - Improved image quality - Improved camera image quality including better consistency of exposure, more realistic flash coloring, improved photos in low light conditions using front camera.
Camera - Pause video recording - Added the ability to pause video recording with a convenient pause/resume button on the viewfinder.
Updated Phone dialer - Updated Phone dialer with a new graphical layout and colors to improve consistency and usability.
Motorola Alert application - New Motorola Alert application sends periodic alerts with your location to your selected contacts. Now available for download from the Google Play Store.
ROM LINK
212.44.28
md5: d1fb4c2259855abf74dfadbad5ccdbc2
FIRMWARE LINK
LINK
-----------------------------------------------------------------
BIG thanks to:
iKrYpToNiTe
chad.goodman
NineInchNails
Rizal Lovins
ibanez7
motofirmware.center
JustCMH
HOT-SPOT UNLOCK:
iKrYpToNiTe said:
All you have to do is add net.tethering.noprovisioning=true to your build.prop file and then you can remove or freeze the entitlement check app if you want to. Sprint model requires ro.mot.tether_dun_required to change from 1 to 0.
For people who don't want to mess with modifying their build.prop file or use xposed. I made an app which requires Root, that will run a setprop command to bypass the check until you reboot. If you want it to last after a reboot you can select apply of boot to run the command after every reboot. This was tested and confirmed by cvhovey thanks to him for testing it for me, since I have free tethering. This is my first app so I hope you Enjoy it! I want to say thanks to jcase's slapmymoto and the developer of adaway, I used their github sources as references when I couldn't get something working. Also androidicons for the icon template, and Poliva for setpropex, and jduck for getting setpropex working on KitKat.
Download Links
v1.2 http://www.androidfilehost.com/?fid=23501681358557764(v1.2 is signed with a different key than v1.0/v1.1 so it will display a msg box telling you this just click okay)
Click to expand...
Click to collapse
RECOVERY LINKS
CWM Advanced Edition- PhilZ Touch
TWRP
SUPERUSER LINKS
SuperSU
CWM Superuser (Koush)
DID YOU MAKE AN EXPENSIVE BRICK?
[HOW-TO] Resurrecting A Bricked Moto X
FEW WAYS TO GET BACK TO STOCK
Easy Guide to Restore Stock Firmware on Moto X using RSD Lite
Moto X Toolkit v1.4.3 [Backup/Restore,Drivers,Return to stock,Root,Bootani]
Script FlashFirmware (simple and safe method to flash firmware)
Getting a moto x back to stock on mac os x
BAD BATTERY DRAIN LATELY? TRY THIS
hardware reset of the processor and terminates all running commands
LEAVING THIS HERE IN CASE I FORGET HOW TO TAKE A DUMP
Code:
[B]dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/System.img.ext4
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/Boot.img[/B]
Thanks for this! Thanks soo much for the hard work!
FINALLY! The first rom for the Sprint variant :').... I Love you! haha.
They are both up. md5's should be posted right, they were manually entered. I'm carving pumpkins with the boys, so........hopefully all is good. If not, let me know and I'll attack it when able to.
AbstractXart said:
FINALLY! The first rom for the Sprint variant :').... I Love you! haha.
Click to expand...
Click to collapse
pfft, and mine was what?
looks good gokart
shabbypenguin said:
pfft, and mine was what?
looks good gokart
Click to expand...
Click to collapse
Just trying to get things going...lol. Didn't see anything for Sprint ver, must have missed yours? BTW....I seen a shabby looking penguin on a program to turn system.img into system files in the kithcen......is that you?
gokart2 said:
Just trying to get things going...lol. Didn't see anything for Sprint ver, must have missed yours? BTW....I seen a shabby looking penguin on a program to turn system.img into system files in the kithcen......is that you?
Click to expand...
Click to collapse
nah, the last big script i did for people was teh first nexus toolkit, nowadays i hop around trying to help out unloved devices (hence teh name of the team i made Official Unloved Devices Hit Squad ). people needed this anyways, my stock rom was based on the pre-ota camera fix apparently. i had considered getting this phone on republic wireless so i wanted to scope out how development was coming, saw nothing was going on and figured id help out .
shabbypenguin said:
pfft, and mine was what?
looks good gokart
Click to expand...
Click to collapse
Wha?! I never saw it Shabby. My bad, let me rephrase,
FINALLY! The second rom for the Sprint variant :').... I Love you! haha.
Hey guys, I just wanted to update and say it won't boot on the Verizon dev edition like the T-mobile rom will. It freezes for me on the Moto Earth boot animation. Noo! Well darn, I was wanting to try the sprint rom to see if I could get google wallet tap to pay working on my vzw dev phone since no one has figured out how to make tap to pay work on the non-sprint variants.
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
skiwong20 said:
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
YES!!!! It worked!!! LOL. Anyway, have you/anyone noticed anything when trying to alter the stock boot.img? Seems like anything I tried (not a whole bunch really) with the kernel/boot.img made it non-bootable? Pretty much if it hits the bootloader unlocked screen and doesn't vibrate.....its a no go? Wondering if theres some type of checksum for the boot.img? Not too sure about wallet ATM. Don't really use it, and this is based off the OTA so....I'd assume it should be fine? I remember some stuff way back on this, may have to step back and see if there's something to utilize. This isn't my first rodeo.....but it's the first one I've entered.:laugh:
gokart2 said:
YES!!!! It worked!!! LOL. Anyway, have you/anyone noticed anything when trying to alter the stock boot.img? Seems like anything I tried (not a whole bunch really) with the kernel/boot.img made it non-bootable? Pretty much if it hits the bootloader unlocked screen and doesn't vibrate.....its a no go? Wondering if theres some type of checksum for the boot.img? Not too sure about wallet ATM. Don't really use it, and this is based off the OTA so....I'd assume it should be fine? I remember some stuff way back on this, may have to step back and see if there's something to utilize. This isn't my first rodeo.....but it's the first one I've entered.:laugh:
Click to expand...
Click to collapse
what command are you using to pack the boot.img?
skiwong20 said:
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Yeah I wipe three times before flashing and I wiped cache and dalvik again before booting. I wonder what the issue is. I downloaded the odex and not deodex but I don't see it being the difference between booting and freezing. Hmm. I'm back on the T-Mobile rom now. I'll have to try again with the deodex tomorrow
shabbypenguin said:
what command are you using to pack the boot.img?
Click to expand...
Click to collapse
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
jimmypop13 said:
Yeah I wipe three times before flashing and I wiped cache and dalvik again before booting. I wonder what the issue is. I downloaded the odex and not deodex but I don't see it being the difference between booting and freezing. Hmm. I'm back on the T-Mobile rom now. I'll have to try again with the deodex tomorrow
Click to expand...
Click to collapse
I recommend wiping system and data too and trying. Just make a backup first. And/or try using your normal boot.img instead of the one in the zip.
gokart2 said:
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
Click to expand...
Click to collapse
i take it then you arent packing the Device tree file to the boot.img.
http://pastebin.com/tSGxTmYq save this script, run it against stock boot.img. youll get a DTB.img, extract your boot.img, edit what you want in ramdisk or swap zimages. then use a modified mkbootimg to include the dtb file as part of it all
gokart2 said:
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
I recommend wiping system and data too and trying. Just make a backup first. And/or try using your normal boot.img instead of the one in the zip.
Click to expand...
Click to collapse
I got the sprint deodex rom booting on my vzw dev edition doing like you said. But sadly I found google wallet would not work. It just sat saying "finishing up a few things." So I guess unfortunately there is a hardware issue preventing wallet from working on the non-sprint variants. That sucks!!!
I don't understand why but I noticed between the t-mobile, verizon, and sprint roms that the signal bars are slightly different on every one. Sprint's seems to be stretched out a little more and have an extra bar or two. I hate all of them though because the grey has some funky white lines through it where the separations are instead of being solid grey. I don't know what was wrong with the stock android signal bars that none of the carriers wanted them
I have a question regarding safestrap, can I use it to unlock my bootloader and just flash this to my nand? I dont want to waste my space on rom slots :\
d4mi3n said:
I have a question regarding safestrap, can I use it to unlock my bootloader and just flash this to my nand? I dont want to waste my space on rom slots :\
Click to expand...
Click to collapse
Honestly have no clue about SS. I would have to say no. No sure what needs to be done for it to be SS flashable.
Added 4.4 links. Thank abiezer for letting me link to his deodex 4.4 build HERE!
I plan on adding the SPRINT specific firmwares, and more in due time.
I have a vzw max and i recently reverted everything back to stock and unrooted; or so i believed. The kernel still says 3.4.10 etc. and the phone has no signal nor can it find my location. It keeps rebooting every 30 secs or so and no matter what mode I put the device into, it isn't recognized by my PC. the bootloader is locked and I am S-Off. This all happened after I tried to flash CWM's HTC M7 recovery because the Max isn't listed and I couldn't figure out how to flash TWRP. Help please because this is getting crazy and I can't figure out what to do...
bump
nobody at all eh...
LocBox said:
nobody at all eh...
Click to expand...
Click to collapse
So if you boot to bootloader keeps rebooting there too?
Sent from my Nexus 7 using Tapatalk
dude i feel for you.
why did you put m7 cwm on there. clearly not for this device.
can you still get to bootloader? if you can flash the correct recovery! then find a backup someone has done and restore. or flash the correct boot.img
dude here's the correct recovery
http://forum.xda-developers.com/showthread.php?t=2498749
Well the only problem is my any pc won't even detect that it's connected when I plug it into it. So I can't use any fastboot or adb methods and even when I put the phone into fastboot mode it doesn't connect either. I'm able to put it into bootloader mode and it doesn't reset but still no connection; just charges. I've tried flashing through stock recovery manually and it aborts every attempt I'm assuming because my BL is locked..
No it doesn't
dottat said:
So if you boot to bootloader keeps rebooting there too?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
no it doesnt'
LocBox said:
no it doesnt'
Click to expand...
Click to collapse
Ok. I know how we can fix then. Let me pm you
Sent from my HTC6600LVW using Tapatalk
Thanks
Dottat has helped me and not a moment too soon, I was seconds from printing out the return label for HTC and sending it in for a refurb exchange. smbh. thanks man.:good:
dottat said:
Ok. I know how we can fix then. Let me pm you
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
hey mate, whats the secret sauce
Flashing the zip from bootloader ?
pradeepvizz said:
hey mate, whats the secret sauce
Flashing the zip from bootloader ?
Click to expand...
Click to collapse
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
JBS976 said:
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
Click to expand...
Click to collapse
haha, okay chill mate. i was kidding there.
i am guessing it was full flash of rom / kernel using the zip in the bootloader.
pradeepvizz said:
haha, okay chill mate. i was kidding there.
i am guessing it was full flash of rom / kernel using the zip in the bootloader.
Click to expand...
Click to collapse
That is correct, full flash from bootloader. 0P3PIMG.zip on root of sd. and boom with some pow.
JBS976 said:
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
Click to expand...
Click to collapse
I wasn't trying to hide anything. I typically will walk a user through using the encrypted RUU (my person preference as i know it's intact) to restore their phone as long as it can boot to bootloader. I take it offline because the mods didn't take kindly to the encrypted RUU being posted in the past. I don't have an answer as to why that was case so I just keep that part off the main threads. If its someone in need (like the OP) i have no problem helping one on one.
dottat said:
I wasn't trying to hide anything. I typically will walk a user through using the encrypted RUU (my person preference as i know it's intact) to restore their phone as long as it can boot to bootloader. I take it offline because the mods didn't take kindly to the encrypted RUU being posted in the past. I don't have an answer as to why that was case so I just keep that part off the main threads. If its someone in need (like the OP) i have no problem helping one on one.
Click to expand...
Click to collapse
It's cool, I didn't mean it to sound like anything was being hidden, I just like to read all this stuff and take it in for future reference as I don't want to bother you guys unless I just cannot figure it out on my own. Believe me i really appreciate all you guys do on here as this is an invaluable resource if people take the time to read through things. I was unaware that they didn't want the RUU's on here which really sucks because they are nice to have like I had them for the rezound and it came in real handy at times. Not having them for this device yet has been one of the reasons I have been hesitant to do much else than to S-OFF and root. At this point I guess I am waiting for the OTA Kit Kat update then I will probably dive in.
Bryon
JBS976 said:
It's cool, I didn't mean it to sound like anything was being hidden, I just like to read all this stuff and take it in for future reference as I don't want to bother you guys unless I just cannot figure it out on my own. Believe me i really appreciate all you guys do on here as this is an invaluable resource if people take the time to read through things. I was unaware that they didn't want the RUU's on here which really sucks because they are nice to have like I had them for the rezound and it came in real handy at times. Not having them for this device yet has been one of the reasons I have been hesitant to do much else than to S-OFF and root. At this point I guess I am waiting for the OTA Kit Kat update then I will probably dive in.
Bryon
Click to expand...
Click to collapse
Check your pm shortly. S-off later today ?
Sent from my HTC6600LVW using Tapatalk
I had my phone rooted perfectly fine and I accidentally let an update get by me and now it's unrooted Android 12. I really need my boot.img from GN2200_11_C.10 or I need to know where to download a Pretooted GSI image that I can DSU Sideload so I can pull my own boot l.img.. thanks in advance!!
Where? I couldn't find it
ScarletWizard said:
Did u find it
Click to expand...
Click to collapse
No I still can't find this specific one?! Stinks!
termux4life said:
No I still can't find this specific one?! Stinks!
Click to expand...
Click to collapse
I appreciate your help though. Thank you for taking the time to respond back.
termux4life said:
No I still can't find this specific one?! Stinks!
Click to expand...
Click to collapse
Thank you for taking your time to respond though.
I'm looking for a specific boot.img. it's in the title.. you need to use the msm download tool to revert back to stock. Sounds like your partitions are messed up and I assume they weren't backed up. I was hard bricked at one point and the msm tool was the only way for me to fix it all and revert back to stock. Make sure it's the correct msm tool for your phone though.
ScarletWizard said:
Try
Or this
Wipe data after flashy
Wipe data
Too large I got several but too large to attach
Click to expand...
Click to collapse
Can you send me the link for the specific boot.img I'm looking for by chance? It's the 11_C.10 version.
ScarletWizard said:
I locked my Boot loader and now device is ****ed
Click to expand...
Click to collapse
Why you can't just unlock it again? Do you have the the T-Mobile version?
The bootloader is encrypted and OnePlus's token just gives you the private to match the public encryption that keeps the bootloader from being edited. In theory if you can discover what file type one plus's token is in and eextract that and somehow dump your bootloader you could possibly manually decrypt it.
Do you have access to a Personal Computer? I could offer some links to a few programs that may be worth trying. I doubt it could hurt trying.
I could use teamviewer to try to use my tools to force your bootloader to unlock also if you happen to not find a solution.
termux4life said:
Thank you for taking your time to respond though.
Click to expand...
Click to collapse
i have the exact one
termux4life said:
I had my phone rooted perfectly fine and I accidentally let an update get by me and now it's unrooted Android 12. I really need my boot.img from GN2200_11_C.10 or I need to know where to download a Pretooted GSI image that I can DSU Sideload so I can pull my own boot l.img.. thanks in advance!!
Click to expand...
Click to collapse
Pretooted, that's funny as can be. A pretooted sideload so he can pull his own.
Ok so 2 things..
1st: Jayram1408, for being a senior member I'm really surprised you'd laugh at me for asking a question or not knowing something. Usually this is a safe place to learn, ask questions, and receive feedback that's positive and informative. I don't know if you think others will laugh at me with you but I doubt it
2nd: I don't know what is funny in the first place, pre-rooted GSI for DSU Sideloading purposes do exist and that's a fact. It makes it so you can use Partitions Backup & Restore properly when the GSI is loaded. Please read https://forum.xda-developers.com/t/...g-boot-image-and-making-your-backups.4499447/
Hopefully that catches you up with the rest of us and hopefully in the future you are but more helpful then hurtful to members within the community.
Hey All,
I am trying to root my Nord N20, but am getting a bootloop when trying to boot boot_a after flashing a magisk25210canary patched boot_b image over boot_a. I am flashing a patched boot_b image over boot_a because I am too scared to flash magisk patched boot_b over boot_b (which contains the working OS). My version information is:
android 12
Build: GN2200_11_C.11 Kernel:5.4.147-qgki-ga9e7460afd8c