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!
Related
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.
I hoping that someone may be able to help me with this… I recently rooted my note via instructions here and installed CWM and TiBu. So far so good!
I began freezing some of the bloat and then found this post to see what else I could freeze. This is were things went wrong… I guess that I may have frozen something that I shouldn’t have because my home button stopped responding and then the back button took me to a black screen.
At this point I thought that my phone was nearly bricked, so I downloaded the firmware from SamMobile and flashed it. Still have a black screen, but I received a text and pop-up through chomp which let me know that my phone was still alive! I installed Go Launcher and can now can use my phone as 'normal'. However, I no longer have root according to TiBu, CWM and the like. I can still boot into download and recovery modes.
I found this thread, but it didn’t do much for me.
How’s that for an introductory post?!!
:cheers:
CivilE
CivilE said:
I hoping that someone may be able to help me with this… I recently rooted my note via instructions here and installed CWM and TiBu. So far so good!
I began freezing some of the bloat and then found this post to see what else I could freeze. This is were things went wrong… I guess that I may have frozen something that I shouldn’t have because my home button stopped responding and then the back button took me to a black screen.
At this point I thought that my phone was nearly bricked, so I downloaded the firmware from SamMobile and flashed it. Still have a black screen, but I received a text and pop-up through chomp which let me know that my phone was still alive! I installed Go Launcher and can now can use my phone as 'normal'. However, I no longer have root according to TiBu, CWM and the like. I can still boot into download and recovery modes.
I found this thread, but it didn’t do much for me.
How’s that for an introductory post?!!
:cheers:
CivilE
Click to expand...
Click to collapse
Did you have ICS or GB ? BTW all the tools you needed are right here in XDA GNote threads.
http://forum.xda-developers.com/showthread.php?t=1740367
bigjoe2675 said:
Did you have ICS or GB ? BTW all the tools you needed are right here in XDA GNote threads.
http://forum.xda-developers.com/showthread.php?t=1740367
Click to expand...
Click to collapse
ICS. I've seen all of the tools in that thread, but not sure if I need the screwdriver or the hammer to 'get my root back' in this situation. Ultimately I'd like to be able to do it without having to do a full wipe/recovery.
Freezing an app will not brick your phone...
and in this case....you did not need to flash a new firmware. you could have simply pulled the battery, then put it in and booted to recovery to restore a backup.
but of course, the new firmware did break root....
bigjoe is right on the links info. it has all you need to start again.....and I "would" re-root using the odin CWM flash method......
In the general section, under the "galaxy note everything" thread.
All you need is there....g
CivilE said:
ICS. I've seen all of the tools in that thread, but not sure if I need the screwdriver or the hammer to 'get my root back' in this situation. Ultimately I'd like to be able to do it without having to do a full wipe/recovery.
Click to expand...
Click to collapse
Follow the big green arrow for ics rooting (btw if you miss it, do not root)....can i get a Hoot for the Root!
Hammer> CWM install via odin...no wiping
Nail> super user flash with no wiping for Root
Good to go...
gregsarg said:
Freezing an app will not brick your phone...
and in this case....you did not need to flash a new firmware. you could have simply pulled the battery, then put it in and booted to recovery to restore a backup.
but of course, the new firmware did break root....
bigjoe is right on the links info. it has all you need to start again.....and I "would" re-root using the odin CWM flash method......
In the general section, under the "galaxy note everything" thread.
All you need is there....g
Click to expand...
Click to collapse
+100
H--o--o--t !!!!
Bigjoe for moderator !!!
Good to go!! Apparently twlauncher was inadvertently frozen which explains the black screen. Had I realized what the problem was, yes a simple recover from backup might have fixed it.
So tell me this, as I am still learning here... What is the difference in the method in bigjoe's thread vs trying to re-root my phone by the method I used previously? Whenever I tried to install SU after the original method I used, I would get a failed signature error. No problems with using bigjoe's recommendations.
:cheers:
CivilE
bigjoe2675 said:
Follow the big green arrow for ics rooting (btw if you miss it, do not root)....can i get a Hoot for the Root!
Hammer> CWM install via odin...no wiping
Nail> super user flash with no wiping for Root
Good to go...
Click to expand...
Click to collapse
I see what you did there
CivilE said:
Good to go!! Apparently twlauncher was inadvertently frozen which explains the black screen. Had I realized what the problem was, yes a simple recover from backup might have fixed it.
So tell me this, as I am still learning here... What is the difference in the method in bigjoe's thread vs trying to re-root my phone by the method I used previously? Whenever I tried to install SU after the original method I used, I would get a failed signature error. No problems with using bigjoe's recommendations.
:cheers:
CivilE
I see what you did there
Click to expand...
Click to collapse
The difference is ....bigjoe is a god among men, and probably led the Crusades in a previous life.
I'm quite certain he drank beer with Khan and Hun. Now ignore those historical timelines because bigjoe was there ...period !!
Those things, combined with the fact that he invented the first telephone, make him knowledgeable in all things android and beyond ....so take his word for it ...
And ..after every post ..please use the phrase ....." BIGJOE FOR MODERATOR"....
While it isn't the Crusades over again, he certainly deserves to be one.
After all ...he did invent the telephone for cryin out loud .....LOL
Bigjoe for moderator !!!!!.......H...O....O...T !!!
gregsarg said:
The difference is ....bigjoe is a god among men, and probably led the Crusades in a previous life.
I'm quite certain he drank beer with Khan and Hun. Now ignore those historical timelines because bigjoe was there ...period !!
Those things, combined with the fact that he invented the first telephone, make him knowledgeable in all things android and beyond ....so take his word for it ...
And ..after every post ..please use the phrase ....." BIGJOE FOR MODERATOR"....
While it isn't the Crusades over again, he certainly deserves to be one.
After all ...he did invent the telephone for cryin out loud .....LOL
Bigjoe for moderator !!!!!.......H...O....O...T !!!
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"
}
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?
It's not on the net anywhere either, google is not working for the OT Elevate. There are no custom ROMs for the OT Elevate either.
I know that someone has one of these OT Elevate 5017B phones lying around somewhere. Post a stock ROM for download. People are suffering from bricks and soft-bricks. HELP more, we need to start a project making an attempt to catalog stock ROMs for every android device on earth.
There needs to be a larger archive of these ROMS. iOS developers are killing you. They have a database of all of the iOS firmwares, and there is a database of custom firmwares even for the iPhone 6S.
I know that the iPhone's situation is different, that one company designs the hardware and the software, and that everything is proprietary. I also feel there are too many companies making android phones. competition is one thing, but security of an OS is another. different phones from the same year with older versions of the OS on them, not good.
Marshmellow has been released and there are still 2016 phone releases with 4.5 OS on them. That's not secure. Why can't we make Android more secure by building better custom ROMs for more devices? I know there is a big shortage of developers, but you can recruit. Maybe even get funded by an organization, research grant?
Everyone needs more ROMs. Especially for Alcatel OT Elevate. Let's do something about this.
On 3. 1-2-3, Go Team!!!! :highfive: Let's Get It!
I have one of those Alcatel OneTouch phones right now, and I agree completely upon the notion for a catalog of all android devices that can be flashed.
@mU$!c @tyrex420
These Alcatel devices can only get attention if developers have them in their hands to work with. These devices are running a MediaTek SoC and not many developers like to work with those phones because of a lack of source code to work with or incomplete source in some cases. Yes you are correct in saying that Apple is different as it's one software, one hardware but you have to understand Google only set the stage and the companies do the rest. Not every company is Samsung or Sony. Alcatel has a tool which is really good called Mobile Upgrade Tool which has the factory ROM for their devices (which imho they need work on getting those newer devices supported). It works well if you haven't done much modification to your phone. Now the thing is that when those companies take the phones and modify them in some way like in locking the bootloader or hiding fastboot mode (Tracfone,MetroPCS), there's not much that a developer can do about that. Also those companies do not have that same support tool that Alcatel has which re-downloads the factory ROM because they are modified in some way.
Here's the good part about the phone running a MTK SoC. There are third-party tools such as MTK Droid Tools or SmartPhoneFlashTool (SPFT) which enables the users to make factory backups of their ROMs in the event that their devices suffers from a bootloop. What you can now do is become that developer that you are asking for to work on your phone and make something out of it. Be the first to upload a flashable factory ROM for your phone. Create a thread where users can come and post their issues and assist each other positively. It's nothing hard to do unless as I said before the company locks some part of the phone and makes these tools useless. By the way, MTK Droid Tools developer dropped support at Jelly Bean so KitKat and up won't work with the tool as it should.
Again, yes I agree with you in saying it would be nice for a users to find a compilation of ROMs that they can just follow instructions and flash but the thing is source code and users themselves not knowing how to use the tools mentioned above. If you want you can ask me for help in guiding you on how to use the tools. I've been doing this for 3 years now working with MTK and I'm learning something new everyday.
Sorry for my long reply, I hope to see a reply from you concerning getting a factory ROM for this device maybe a thread similar to mine .
@kirito9
Thank you. I learned more in 2 minutes from your reply than in two hours searching the internet. XDA needs more people like you!
-Cheers
bg260 said:
@kirito9
Thank you. I learned more in 2 minutes from your reply than in two hours searching the internet. XDA needs more people like you!
-Cheers
Click to expand...
Click to collapse
You're welcome .
kirito9 said:
You're welcome .
Click to expand...
Click to collapse
I had one of these fall in my lap. Charging port is shot. At least I can remove the battery and charge. I'm trying to see if it's worth fixing. All signs are pointing to no, unfortunately. OEM Bootloader unlock is available but without Fastboot.......
bg260 said:
I had one of these fall in my lap. Charging port is shot. At least I can remove the battery and charge. I'm trying to see if it's worth fixing. All signs are pointing to no, unfortunately. OEM Bootloader unlock is available but without Fastboot.......
Click to expand...
Click to collapse
Hmm so you don't have a working charging/usb port. I doubt you'll be able to do much with this phone in terms of development. Not sure if there is a way to unlock the bootloader from the device itself, doubt it.
kirito9 said:
Hmm so you don't have a working charging/usb port. I doubt you'll be able to do much with this phone in terms of development. Not sure if there is a way to unlock the bootloader from the device itself, doubt it.
Click to expand...
Click to collapse
I'll see if I can get something useful out of it. Maybe a recovery.img, boot.img, system.img. I'll have to use one of those dreadful one-click apps though.
As for the OP I think this is as close as it gets.
http://forum.xda-developers.com/wiki/
Being a public wiki everyone is welcome to add to or amend it.
bg260 said:
I'll see if I can get something useful out of it. Maybe a recovery.img, boot.img, system.img. I'll have to use one of those dreadful one-click apps though.
As for the OP I think this is as close as it gets.
http://forum.xda-developers.com/wiki/
Being a public wiki everyone is welcome to add to or amend it.
Click to expand...
Click to collapse
Yeah although the information is quite old still useful.
Root with Kingroot and backup with flashify haha. But won't you need the unlocked bootloader to root?
Got side tracked. Device currently disassembled, trying to replace usb but it is hard soldered to the Motherboard. Cheap phones....
bg260 said:
Got side tracked. Device currently disassembled, trying to replace usb but it is hard soldered to the Motherboard. Cheap phones....
Click to expand...
Click to collapse
Ahh cheap phone problems. Let me know if you get through.
Successfully rooted with Kingroot v4.92 . I have included others JIC.
I used The paid SuperSUme Pro to eradicate Kinguser from the device. Here are some other options.
http://forum.xda-developers.com/gal...ve-kinguser-replace-supersu-sch-i545-t3334533
After updating SuperSu via the playstore I installed Busybox Pro, but the unpaid version is fine. At which point I updated the SU binaries the "Normal Way" without a hitch.
{
"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"
}
@kirito9
I'll start with a system.img What else do you need?
Thanks
-Bg260
bg260 said:
Successfully rooted with Kingroot v4.92 . I have included others JIC.
I used The paid SuperSUme Pro to eradicate Kinguser from the device. Here are some other options.
http://forum.xda-developers.com/gal...ve-kinguser-replace-supersu-sch-i545-t3334533
After updating SuperSu via the playstore I installed Busybox Pro, but the unpaid version is fine. At which point I updated the SU binaries the "Normal Way" without a hitch.
View attachment 3906591
@kirito9
I'll start with a system.img What else do you need?
Thanks
-Bg260
Click to expand...
Click to collapse
Did you get the the USB removed? Hmm what are we trying to achieve? A full backup or a ROM?
kirito9 said:
Did you get the the USB removed? Hmm what are we trying to achieve? A full backup or a ROM?
Click to expand...
Click to collapse
I wasn't able to replace the USB. Without an unlocked bootloader there is not much I can do. Thought maybe I would help the cause is all. I personally will probably screw with it till it bricks. IDK. Thought someone could at least get a recovery going. I'm not a developer in that sense. I usually just crack open the system.img and add/remove a few thing to my liking. I'll go ahead and dump a system/boot/recovery.img package on AFH if anyone has interest.
bg260 said:
I wasn't able to replace the USB. Without an unlocked bootloader there is not much I can do. Thought maybe I would help the cause is all. I personally will probably screw with it till it bricks. IDK. Thought someone could at least get a recovery going. I'm not a developer in that sense. I usually just crack open the system.img and add/remove a few thing to my liking. I'll go ahead and dump a system/boot/recovery.img package on AFH if anyone has interest.
Click to expand...
Click to collapse
Ahh, that'd be nice. Someone might mess up their stock recovery/boot/system. Please upload and maybe I can try to get a custom recovery for this device. Then make a full backup using the custom recovery.
kirito9 said:
Ahh, that'd be nice. Someone might mess up their stock recovery/boot/system. Please upload and maybe I can try to get a custom recovery for this device. Then make a full backup using the custom recovery.
Click to expand...
Click to collapse
Found something different, the system partition on mmcblk0p33 is 800mb 535 used.
There is also something called custpack on mmcblk0p32 at 1gb total 663mb used. I made an img of both. I'll upload it in a little bit.
Quick question, I have been using furiusisomount with Linux mint cinnamon to rummage around system images. Lately it throws an error and won't mount. Is this familiar to you? I'm not as proficient with the CLI as I'd like to be so I often rely on GUI.
bg260 said:
Found something different, the system partition on mmcblk0p33 is 800mb 535 used.
There is also something called custpack on mmcblk0p32 at 1gb total 663mb used. I made an img of both. I'll upload it in a little bit.
Quick question, I have been using furiusisomount with Linux mint cinnamon to rummage around system images. Lately it throws an error and won't mount. Is this familiar to you? I'm not as proficient with the CLI as I'd like to be so I often rely on GUI.
Click to expand...
Click to collapse
Ok, both images are critical for Alcatel devices running MTK SoC to get it booting. The furiusisomount I'm not familiar with but maybe I can help. What error are you getting?
kirito9 said:
Ok, both images are critical for Alcatel devices running MTK SoC to get it booting. The furiusisomount I'm not familiar with but maybe I can help. What error are you getting?
Click to expand...
Click to collapse
Ok, Here you go. It has boot, aboot, recovery, system and custpack. Are you going to need patitioning info? Be easy if I had adb. But I don't
I'll get back to you on that error. I'm having some other issues and I think it might be systemic. I may have to do a fresh install of Mint.
Let me know what else you need. Happy to help.
https://www.androidfilehost.com/?fid=385035244224385460
bg260 said:
Ok, Here you go. It has boot, aboot, recovery, system and custpack. Are you going to need patitioning info? Be easy if I had adb. But I don't
I'll get back to you on that error. I'm having some other issues and I think it might be systemic. I may have to do a fresh install of Mint.
Let me know what else you need. Happy to help.
https://www.androidfilehost.com/?fid=385035244224385460
Click to expand...
Click to collapse
I think there may be another way to get the partitioning info but let me look into it. Thanks for the files and will let you know if I need anything else .
kirito9 said:
I think there may be another way to get the partitioning info but let me look into it. Thanks for the files and will let you know if I need anything else .
Click to expand...
Click to collapse
See if this is what you need. Created it with DiskInfo Pro. I used a different machine and mounted the system image fine. I thought it was a bad copy because the Build.prop displayed as broken. Then I realized it was just a symlink to the actual build.prop in custpack. At any rate, there's a copy of the build.prop in there as well.
View attachment build.prop-partitions-5017b.zip
I have just purchased the Alcatel Raven A574BL with a Qualcomm 210 chipset . It's a great value running Android N and 2gb RAM, so being able to run a custom recovery will also make it a great value as a developer's tool. At $30 it's basically expendable, so I don't mind risking to brick it. So far I have not been able to find any root support for this device on Google. If anyone can help me get started with this, or point me in the right direction, it will be much appreciated.
mscott9437 said:
I have just purchased the Alcatel Raven A574BL with a Qualcomm 210 chipset . It's a great value running Android N and 2gb RAM, so being able to run a custom recovery will also make it a great value as a developer's tool. At $30 it's basically expendable, so I don't mind risking to brick it. So far I have not been able to find any root support for this device on Google. If anyone can help me get started with this, or point me in the right idirection, it will be much appreciated.
Click to expand...
Click to collapse
My understanding is the system is locked down and cannot be done. I've been wanting to do the same on same phone in your post.
thanks for the reply. i am disappointed to learn that it's impossible to root this phone... what i really need is a phone which is under $50 and can be easily rooted. also otg support will be a great bonus. it's totally ridiculous to pay up to $500 for a pixel... just so i can have root functionality. even if i could find a good deal on a recertified, most likely it won't support the latest android OS. if anybody out there can help me with this issue... which really shouldn't be an issue at all, it will be much appreciated. i'm trying to run android N at a minimum.
mscott9437 said:
thanks for the reply. i am disappointed to learn that it's impossible to root this phone... what i really need is a phone which is under $50 and can be easily rooted. also otg support will be a great bonus. it's totally ridiculous to pay up to $500 for a pixel... just so i can have root functionality. even if i could find a good deal on a recertified, most likely it won't support the latest android OS. if anybody out there can help me with this issue... which really shouldn't be an issue at all, it will be much appreciated. i'm trying to run android N at a minimum.
Click to expand...
Click to collapse
Search on the TWRP website, if a phone has TWRP available for it, it will also have a rooting solution.
The rest like searching one with Android N or above, I leave it to you.
HIT THANKS IF FOUND USEFUL
How do I root my Alcatel Raven
https://clickitornot.com/unlock-bootloader-on-alcatel-device/
Alcatel raven
Has anyone found a way to unlock bootloader and root this phone yet?
crazypwn said:
Has anyone found a way to unlock bootloader and root this phone yet?
Click to expand...
Click to collapse
I would like to bump this thread. I am in the same boat. Googling has gotten me now where.
Possibly
Although KingRoot seems to have found an exploit, it is iffy. The problem seems to be lack of supported fastboot. Not sure about Oem unlocking, though the option still is under settings>dev options>allow oem unlock(need dev access settings>about phone>build number tap 7x) Without full fastboot support, I can't see if it does anything. There is a possible solution, but since I'm new I can't share the link
Without a potential hard brick and basically cracking the OS, root is improbable. I nay have a solution. Still working on it.
Possible solution
King root seems to have taken down the exploit, since it rarely worked. There is a post on stupdroid that may have a solution. From what I can tell(I own the A574BL), although the OEM unlock function works, fastboot either does not work, or is locked down
To root your phone there are many way.
I can help you rooted your phone by getting boot.img
If you give boot.img there might be a hope
and to get TWRP
I'll need to port it by using your stock recovery.img as base.
or or or or....
You can make it by scracth
Reeak
I don't know of a way to get boot img. How do I make it myself?
or just give me your firmware files
Re
Peak.Krittin said:
or just give me your firmware files
Click to expand...
Click to collapse
How do I get those? Once again, these things are not publicly available for my device
clcombs262 said:
How do I get those? Once again, these things are not publicly available for my device
Click to expand...
Click to collapse
Well You got no hope right now.
If you came back with boot.img I will make the magic happen
Peak.Krittin said:
To root your phone there are many way.
I can help you rooted your phone by getting boot.img
If you give boot.img there might be a hope
and to get TWRP
I'll need to port it by using your stock recovery.img as base.
or or or or....
You can make it by scracth
Click to expand...
Click to collapse
you seem very helpful..
I just got this phone at BB for $15, on sale for 20 then another 5 email credit. Still using my Alcatel Ideal for phone use with Red Pocket AT&T sim for now, just using the Raven as kind of small wifi tablet. But I really like it after having gotten set up just right I'm pretty satisfied even with it not rooted. I'm watching this thread though, I'd probably be all over it if someone comes up with something. Good luck!
Maxxvds said:
https://clickitornot.com/unlock-bootloader-on-alcatel-device/
Click to expand...
Click to collapse
I have an Alcatel ZIP (A576BL), and I find it odd that you can root Alcatel's other devices and ported re-badged phones (ex ZTE Blade) but not THIER phones...
You can port TWRP recovery from alike devices with same chipset , android and kernel version etc. Also you can try 'systemless root' , for example Magisk.
Working with ADB Shell
So having just finished successfully rooting the Alcatel 5059r last night I was hoping I'd have some luck with the Raven. However I have not! At the moment I've hit a wall working with ADB Shell commands, hoping to push, move, mount/remount, and get a root out of it. As i've exhuasted the extent of my tools so down to the nitty gritty. So the problem I'm having with the ADB Shell end of things is that although I've got the proper commands nailed, I can't seem to mount/remount my system folder into read/write. Thats not a huge surprise considering I have no access beyond user. I have however found several folders and files of interest. I can manipulate the oem folder, but honestly at this point the easiest thing would justbe for me to move SuperSu Binary or MagiskSU.zip from storage or SD to the proper folders. As this is really the first time I've had to resort to such methods, and the literature on the subject is at first glance somewhat lacking; as it always is when things get this specialized.
If anyone has any ideas of how to go about using ADB Shell commands or any other method I haven't tried (all in one tool, platform tools, alcatel flasher, sp flasher, odin, frp hijacker tools ect) Keep in mind this phone at this moment in time doesn't support SD updating thru recovery, fastboot/bootloader/download is locked away somewhere, and yes ADB Sideloading methods as well. I'm willing to try anything and I'll put the time in and exhaust any ideas you guys may have for me!
{
"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"
}