Related
So I've been trying to root my thunderbolt for about a week with no success.
At first I used the method here: http://forum.xda-developers.com/showthread.php?t=1005292
It has continually failed on step 2, tried on different computer also. No luck.
I gave up on rooting it for a few days/
Since the first step went through I am downgraded, running 1.03.605. It's got quite a few bugs and when I try to software update from the phone nothing is found. All I really wanted was to get it to the current firmware to fix connectivity bugs but after searching high and low I still have no idea how to/if it is possible.
I assumed I may have to just root it at this point, so I gave the manual root on theMikMik a shot. While setting up my ABD everything runs smooth until I try to enter commands into abd. I get permissions denied, every time. I've tried looking for an answer to this with no luck. Guide I used found here: http://www.themikmik.com/forums/viewtopic.php?f=66&t=256
So my main question, is there any way to get the latest firmware onto my phone without rooting? I've tried downloading an update, naming it update.zip then updating from bootloader with no luck.
If not, what the hell am I doing wrong that is denying me permission in ABD. I've turned anti-virus off, rebooted etc.
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Edit:
While that may should work, I believe you could start from the beginning with Step 1 using the link I just posted as well. Just don't flash the old firmware (1.0.3.605 that you currently have) after you go through that for any reason (see: http://forum.xda-developers.com/showthread.php?t=1008824).
Absolute_Zero said:
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Click to expand...
Click to collapse
*Facepalm*
So I tried what you said from that guide, step 5 failed for me. So I tried from the beginning...still failed.
So, I decided to record it and hopefully you can tell me what I'm doing wrong.
Link: http://www.youtube.com/watch?v=o2AFZEIVIio
Figured that'd be a better way to get the help I need with less reading on your part.
Sorry, I was commuting home from work.
According to the output of "adb shell" you're either already rooted or psneuter has already been run since boot. (note the "#" output instead of "$").
There's no reason to run psneuter to gain permroot again. So once you see that pound sign, start from a two steps down where it says "/data/local/busybox md5sum /data/local/misc.img". IOW, skip that particular "/data/local/psneuter" step.
And I would highly recommend that if you are going to copy/paste, only copy one line at a time to prevent errors.
Off to grab dinner. I'll check back later when I can but hopefully you will be good from here on out.
Edit:
I'm perfectly happy with walking you through it (and I believe you should be fine after this post anyway) but if you still wanted to use that easyroot method that you started with you might want to read this if you haven't http://bit.ly/qsvOkN. I didn't use that easyroot method but it looks like if a step fails, people just run it again until it works. /shrug
I like adb and people should know how to use it anyway.
Hi everyone,
I have a Sony Tablet S with Android Version 4.0.3 release 5a and I am having problems with the Android Software, the programs such as browser, games even android base applications keep crashing. The device is still under warranty and I sent it for repair however the service here requested around 100$ for software installation as it is not under warranty. This is too much for me so I decided to do it myself however. I have searched this forum and many more to find a solution however even I have tried every step described in forums several time I could not be able to reinstall latest ROM from SD Card. I really desperately need some help here as this device is purchased solely for my daughter who loves android games alot.
I really appreciate any help you may provide.
Thanks.
Aktemur said:
Hi everyone,
I have a Sony Tablet S with Android Version 4.0.3 release 5a and I am having problems with the Android Software, the programs such as browser, games even android base applications keep crashing. The device is still under warranty and I sent it for repair however the service here requested around 100$ for software installation as it is not under warranty. This is too much for me so I decided to do it myself however. I have searched this forum and many more to find a solution however even I have tried every step described in forums several time I could not be able to reinstall latest ROM from SD Card. I really desperately need some help here as this device is purchased solely for my daughter who loves android games alot.
I really appreciate any help you may provide.
Thanks.
Click to expand...
Click to collapse
hello,
try a hard reset. hold VOL up + POWER and when you see the logo sony release the VOL up button. then choose a factory reset. do not have to install from sd card.
Already tried hard and soft reset. Doesn't work.
I will try to describe the problem in full detail. I have weird error messages like "Google Play Store stopped working" "browser stopped working" "clock stopped working" and such error messages and when I try to uninstall programs i can uninstall them however when the tablet restarts they are all there, I think machine resets it self. If i try to uninstall a program called "Ustream" the tablet immediately goes off, and restarts resetting it self again. Even the soft and hard reset can not solve the problem. I have tried to boot the device, it says it is booted (I have managed to run adb and flash tools) how ever when the tablet restarts it again resets it self having the exact same situation as before. I have downloaded the official R5A update from the Sony Website when ever i try to install update from SD, the machine stops saying the operation is aborted due to some error. There must be a way to reset this machine to what ever it was.
Aktemur said:
I will try to describe the problem in full detail. I have weird error messages like "Google Play Store stopped working" "browser stopped working" "clock stopped working" and such error messages and when I try to uninstall programs i can uninstall them however when the tablet restarts they are all there, I think machine resets it self. If i try to uninstall a program called "Ustream" the tablet immediately goes off, and restarts resetting it self again. Even the soft and hard reset can not solve the problem. I have tried to boot the device, it says it is booted (I have managed to run adb and flash tools) how ever when the tablet restarts it again resets it self having the exact same situation as before. I have downloaded the official R5A update from the Sony Website when ever i try to install update from SD, the machine stops saying the operation is aborted due to some error. There must be a way to reset this machine to what ever it was.
Click to expand...
Click to collapse
If you have adb, you can try to root tab and apply the backdoor patch.
Sony Tablet S cihazımdan Tapatalk kullanılarak gönderildi
smgdev said:
If you have adb, you can try to root tab and apply the backdoor patch.
Sony Tablet S cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
I have already tried that. The adb, flasher and other tools that I have found in this site. All in one tool says it has succesfully rooted the device but whenever it boots it restores itself to a previous unknown backup with all the applications installed and I guess not rooted state. I have used the flasher yet it needs rooted device. I have tried to update the system from SD, it says the software is low version (5A). I can not do anything. There must be a solution for this.
Aktemur said:
I have already tried that. The adb, flasher and other tools that I have found in this site. All in one tool says it has succesfully rooted the device but whenever it boots it restores itself to a previous unknown backup with all the applications installed and I guess not rooted state. I have used the flasher yet it needs rooted device. I have tried to update the system from SD, it says the software is low version (5A). I can not do anything. There must be a solution for this.
Click to expand...
Click to collapse
After attempting root the tablet is rebooting into the other partition. (There are two system partitions). Can you try rooting again and on the last reboot boot into recovery and try to install R5a twice in a row without restarting from the recovery menu. Hopefully this will catch the system switch and install R5a on the other system
stifilz said:
After attempting root the tablet is rebooting into the other partition. (There are two system partitions). Can you try rooting again and on the last reboot boot into recovery and try to install R5a twice in a row without restarting from the recovery menu. Hopefully this will catch the system switch and install R5a on the other system
Click to expand...
Click to collapse
I think I have rooted the device asthere is a "device manager" in the security options. However adb programs fails to recognize the device. I have installed the driver several times, restarted the computer how ever it did not change. Last time I was able to see the device in the adb device list. But i do not know what I have done to achieve this as I have tired many options. Can you describe me how to do that step by setp?
Aktemur said:
I think I have rooted the device asthere is a "device manager" in the security options. However adb programs fails to recognize the device. I have installed the driver several times, restarted the computer how ever it did not change. Last time I was able to see the device in the adb device list. But i do not know what I have done to achieve this as I have tired many options. Can you describe me how to do that step by setp?
Click to expand...
Click to collapse
EDIT: I have AIO tools and flasher and ADB automatic driver instlaller. Now ADB Automatic installer worked just fine the adb devices i can see the device serial number. There is an "android device manager" option which I have enabled from security settings in my tablet. USB debugging mode is active however the S.onyTablet.S allinone v6.5 by konrad plasczykowski can not flash the tablet, it can not find the tablet. when i boot in to recover i have 3 options listed.
1. restart device
2 update sysstem from SD cARD
3 Reset to factory settings
when i choose update system from SD cart i see" Erohibit update as a result of checking versdion or base sku insallation aborted." message what does that mean?
there are no other options. how can i continue on...
Aktemur said:
EDIT: I have AIO tools and flasher and ADB automatic driver instlaller. Now ADB Automatic installer worked just fine the adb devices i can see the device serial number. There is an "android device manager" option which I have enabled from security settings in my tablet. USB debugging mode is active however the S.onyTablet.S allinone v6.5 by konrad plasczykowski can not flash the tablet, it can not find the tablet. when i boot in to recover i have 3 options listed.
1. restart device
2 update sysstem from SD cARD
3 Reset to factory settings
when i choose update system from SD cart i see" Erohibit update as a result of checking versdion or base sku insallation aborted." message what does that mean?
there are no other options. how can i continue on...
Click to expand...
Click to collapse
After the update fail. Use adb pull /tmp/recovery.log and post it here and I will see what is happening
The flashing operation fails as the system can not access to the specified directory. Whenever I run the flashing tool the command windows background turns to red and I see this error. ADB can list the device yet I can not flash it.
By the way I have to reinstall all the drivers everytime I connect the tablet to PC, if I remove the cable and re mount it adb fails to list the device.
Hello,
I've been happily using my Kindle HDX 7 for a bit over a year now (13.2.2.6 with Safestrap 3.75 and Nexus Rom), but having recently bought the new chromecast I decided to upgrade to a 4.4 based Rom to use the screencast feature.
However both normal OTA updates and rolling back (to unlock the bootloader) using this method have failed.
(After a factory reset I'm now on stock 13.2.2.6.)
When trying to update manually it never recognizes the .bin in internal storage and just asks for wifi, and when OTA updating i get "last update" failed.
I have re-enabled OTA updates using the toolkit (thats how i disabled them in the first place) but I think that didn't really work.
Any ideas on where to go from here? How exactly does the toolkit disable OTA updates? Can I somehow reenable them manually?
Thanks!
Well, what exactly have you done? The method for 3.2.6 in the thread you linked to requires Safestrap to be removed (ensure you remove secondary slots before you un-install Safestrap via its app!), also keep WLAN off/flight mode active, etc.
Note that getting update via OTA without knowing the current status of your HDX comes with a high brick risk, so I would NOT recommend it.
Cl4ncy said:
Well, what exactly have you done? The method for 3.2.6 in the thread you linked to requires Safestrap to be removed (ensure you remove secondary slots before you un-install Safestrap via its app!), also keep WLAN off/flight mode active, etc.
Note that getting update via OTA without knowing the current status of your HDX comes with a high brick risk, so I would NOT recommend it.
Click to expand...
Click to collapse
I have removed Safestrap before attempting the downgrade and Flightmode on.
In the update menu I just have the Check for Update (or something like that) button that asks for Wifi when pressed. It doesn't seem to recognize the .bin I've placed in the internal storage.
grarrrgh said:
I have removed Safestrap before attempting the downgrade and Flightmode on.
In the update menu I just have the Check for Update (or something like that) button that asks for Wifi when pressed. It doesn't seem to recognize the .bin I've placed in the internal storage.
Click to expand...
Click to collapse
Did you follow all steps mentioned in the thread you linked to?
I.e. after preparation you mentioned (e.g. re-enabling OTA via HDX Toolkit) unzip the rollback.zip to a Folder on your PC, put the 3.1.0-update file in the same folder, execute the install.bat (with the HDX connected by USB, and USB debugging enabled in Fire OS), reboot the HDX, then copy the update file to the root of the sdcard, then wait and see if the update occurs?
Some info to read also in this thread (page 2 is about 3.2.4 users who can use the rollback Images by @ggow, you can NOT use them on 3.2.5/3.2.6!).
Cl4ncy said:
Did you follow all steps mentioned in the thread you linked to?
I.e. after preparation you mentioned (e.g. re-enabling OTA via HDX Toolkit) unzip the rollback.zip to a Folder on your PC, put the 3.1.0-update file in the same folder, execute the install.bat (with the HDX connected by USB, and USB debugging enabled in Fire OS), reboot the HDX, then copy the update file to the root of the sdcard, then wait and see if the update occurs?
Some info to read also in this thread (page 2 is about 3.2.4 users who can use the rollback Images by @ggow, you can NOT use them on 3.2.5/3.2.6!).
Click to expand...
Click to collapse
It sometimes takes several (5-15) minutes for FireOS to recognize a properly formatted update file. Also verify the md5 of the 3.1.0-update file (c49c0363de4d8dfa5c87c1bdb88aa2ba) on you device using ES File Explorer or a similar tool. There are comparable tools to validate file integrity on Windows (eg: HashTab).
If all else fails a factory reset from the native Kindle recovery menu (accessed via <power>+<vol-up>) usually resolves the unrecognized update problem. However, factory resets often manifest additional problems that can leave your device is an unstable (potentially unrecoverable) state. Only take this step as a last resort! Make sure Safestrap is full removed before attempting a reset (guaranteed brick). Don't attempt a factory reset if gapps is/was installed on FireOS; lots of bad outcomes.
I followed the instructions in the linked thread, yes.
Also tried waiting about 10 minutes but no dice. The checksum is correct as well, I just checked.
Before I tried the downgrade, I thought about just updating it normally, but the normal OTA updates wouldn't work either. That made me think that they somehow didn't get re-enabled correctly. Would a factory reset restore OTA updates if they had been disabled with e.g. the HDX Toolkit?
grarrrgh said:
I followed the instructions in the linked thread, yes.
Also tried waiting about 10 minutes but no dice. The checksum is correct as well, I just checked.
Before I tried the downgrade, I thought about just updating it normally, but the normal OTA updates wouldn't work either. That made me think that they somehow didn't get re-enabled correctly. Would a factory reset restore OTA updates if they had been disabled with e.g. the HDX Toolkit?
Click to expand...
Click to collapse
It may - as reported by other respected contributors. However, be aware of of the associated risk. I wouldn't characterize it as 'high' but also not insignificant. Fortunately, 3.2.6 is easy to root if you need to make repairs assuming you get past the grey logo. Make sure 'USB debug' in enabled in FireOS.
I don't believe anyone has cataloged the technique(s) used to disable OTA by HDX Toolkit. Casual observation of console output suggests a shotgun approach disabling multiple services and renaming files. Errors are often logged but quickly roll off the screen. Me thinks it would be tough to reverse engineer without a fair bit of time and effort.
Didi you check name of /system/app/com.amazon.dcp.apk ?
Davey126 said:
It may - as reported by other respected contributors. However, be aware of of the associated risk. I wouldn't characterize it as 'high' but also not insignificant. Fortunately, 3.2.6 is easy to root if you need to make repairs assuming you get past the grey logo. Make sure 'USB debug' in enabled in FireOS.
I don't believe anyone has cataloged the technique(s) used to disable OTA by HDX Toolkit. Casual observation of console output suggests a shotgun approach disabling multiple services and renaming files. Errors are often logged but quickly roll off the screen. Me thinks it would be tough to reverse engineer without a fair bit of time and effort.
Click to expand...
Click to collapse
I've now done the factory reset via the stock amazon 'recovery'. Kindle starts up normally, but still does not recognize the update .bin. In the system update menu there's only the "Check Now" Button (Which asks for wi-fi when pressed), but no option to do a manual upgrade.
I've tried enabling some services other users on this site reported to be connected with OTA updates, but no luck.
Any ideas?
grarrrgh said:
I've now done the factory reset via the stock amazon 'recovery'. Kindle starts up normally, but still does not recognize the update .bin. In the system update menu there's only the "Check Now" Button (Which asks for wi-fi when pressed), but no option to do a manual upgrade.
I've tried enabling some services other users on this site reported to be connected with OTA updates, but no luck.
Any ideas?
Click to expand...
Click to collapse
Thoughts:
- reboot, keep flight mode enabled, enable WiFi (obviously won't connect but should turn on radio) and try again
- as above but disable or move away from registered network(s) then disable flight mode
- as above but disable flight mode for 30-90 seconds. Not enough time to receive an OTA but some old reports indicated connectivity was needed
Davey126 said:
Thoughts:
- reboot, keep flight mode enabled, enable WiFi (obviously won't connect but should turn on radio) and try again
- as above but disable or move away from registered network(s) then disable flight mode
- as above but disable flight mode for 30-90 seconds. Not enough time to receive an OTA but some old reports indicated connectivity was needed
Click to expand...
Click to collapse
When trying to update with wifi connected, I immeadiately get "Last update failed" and a "Retry" button.
I had a look at the HDX Toolkit when re-enabling updates and it seems to throw some kind of error message regarding a missing file: com.amazon.dcp.apk .
(Sadly it overwrites output so I can always only get a glimpse, is there a way to log adb commands or something?)
Is that file needed for OTA updates and could I somehow replace it?
Edit:
ONYXis said:
Didi you check name of /system/app/com.amazon.dcp.apk ?
Click to expand...
Click to collapse
I've only now seen your comment, that file is indeed not there.
I'm looking into that now, thanks!
Edit 2:
This seems to have solved it! Apparently the Toolkit was unable to rename the backup apk *.old to *.apk and did throw an error message but it scrolled by so fast I didn't see it.
Updating to 13.3.1.0 now and then I can hopefully unlock my bootloader.
Thanks everyone!
Hi, I am trying to unlock a Galaxy J1 Ace SM-J111F/DS for my colleague. The phone belonged to his younger brother who had passed away in an accident, now that he's gone, we have no information as to now to unlock his phone.
I have tried researching and searching around for methods but to no avail. I was hoping maybe someone here could provide some assistance
A factory reset is out of the question as he needed to access information stored inside the phone
Some device details:
Device is locked by a pattern lock
Unable to unlock via Google account(No one in his family knows his account name/password)
Phone is not Rooted
Phone is FRP Locked
Things I have wanted to try and done so far:
Intended to flash a bypass to unlock the lock screen
Attempted to flash a custom recovery in order to flash the bypass, however FRP is locked and it does not allow a custom recovery to be flashed
Attempted various methods of "security exploits" to unlock, but appears to be patched on current firmware
Tried to search methods of unlocking FRP, however all the methods I've seen so far requires access to developers option, or requires a flash of stock firmware.
Tried accessing device via ADB, however it does not work as USB debugging is not enabled
I'm currently out of options trying to do this by myself, we would really appreciate it if someone could help us out in this
If powered on, and plugged in to PC, is it 'seen' at all?
robneymcplum said:
If powered on, and plugged in to PC, is it 'seen' at all?
Click to expand...
Click to collapse
Yes, it is "seen", but I can't do anything else to it
If it is seen, there is a chance you can get data off it.
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Chilli71 said:
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Click to expand...
Click to collapse
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
XenoJin said:
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
Click to expand...
Click to collapse
Ill jump in this one to. im in a similar situation. I have a lg g vista that no conventional method is working to bypass frp. Device is not encrypted. My prob is. I believe if i can downgrade back to stock kk which the phone was released with it didnt hve frp then so bam im in. But lgflash tool wont downgrade. Always errors. Loads of diffrent settings have been made. Also followed guides to a t.
But in ure case to if it is possible to dlmode and odin back to kk or earlier u should the be able to skil the google login totally. I dont know if ure device came with kk from factory or lolipop. Frp was implemented in loli so kk should be good. Maybe
Two comments:
1) I have a Huawei G8 in front of me. I worked all weekend with it with bootloader/fastboot. I wanted to test the lock screen/adb behavior, But to my surprise ADB does not find it w/ and w/o lockscreen. --> There are different possibilities why the phone does not show up (it worked in the past with this phone/notebook, but quit working). Before you flash make sure that your setup is working (best with an identical mobile). It seems that USB connection can behave different in Bootloader/Recover/Android OS mode.
2) I made a dirty flash (w/o erasing flash) of Lollipop over Marschmallow last weekend. The result was that many directories including SDCard0 where not accessible. Also user data was not accessible. And you have always the chance that you mess something up when flashing and you loose the content.
If the data is really important your friend could pay a data rescue company (if you don't loose your face). I'm pretty sure that programs exist that can be loaded into RAM with bootloader (fastboot boot) that provide an interface to the PC (in the easiest case, adb again).
Chilli
Seeing how this phone just recently came out in January I haven't really found too much info out there so maybe this can be a start.
I've tried to unlock the bootloader but couldn't get fastboot to work and I tried kingroot and that failed. iIt has 12 requests for this phone so far.
So I'm pretty stuck right now on what to do I'm kinda a noob so maybe y'all can help me out a lil on what to do if anymore info is needed please let me know.
Thanks in advance
Greetings, I am noob too, but I am learning. I cannot answer your question about unlocking the bootloader, however, someone gave me an Alcatel Verso that had frp lock screen. Got limited access and installed an app called quickshortcutmaker. This allows running all the activities. There is a system app on mine called engineer mode. This reveals the actual file system as well as other info.
It appears there is not a reboot bootloader mode, it does have reboot recovery, but also I do not think it has fastmode. There is another mode called download mode, but I have not successfully used this for anything. Also, connecting usb abd in recovery mode yields device unauthorized.
If you are interested, I'll explain how I got frp partially bypassed. Added emergency contact, added an email, a prompt came up asking me which service to use, there were like four options like google, etc. I chose one I had not heard of that had the word executive, because it sounded official. When I chose it, another prompt came up saying that in order to use this service I had to set up a lock screen, make sure func is enabled. When I then turned the screen off and back on, I had a google search option from the lock screen. Pressed it and said "open settings", enabled install of unknown sources, used google search and said "open chrome". Used chrome to download quickshortcutmaker. Used google search and said "open file manager". Used file manager to install quickshortcutmaker. At this point I could have just used the phone from there, however... I added quickshortcutmaker to the func lock screen list by using google search to open settings. Then from the lock screen, I could launch quickshortcutmaker (or use google search). I then used quickshortcutmaker to run 'joy launcher' and voila, in. However, only the back button worked, and if I tried to log into google, it would bring up the frp lock screen. So, using the quickshortcutmaker, I ran every activity on the phone, and using the engineermode system app (I am pretty sure it was that one) I toggled an option called 'demo mode'. Upon exiting this system app and pressing the square button next to the home and back button, I saw an option to accept user agreement, or something like that. I scrolled down and checked the box, and voila, frp lock totally gone, and now I can log into google.
Now I am trying to root, but first I must unlock the bootloader.
diorthotis said:
Greetings, I am noob too, but I am learning. I cannot answer your question about unlocking the bootloader, however, someone gave me an Alcatel Verso that had frp lock screen. Got limited access and installed an app called quickshortcutmaker. This allows running all the activities. There is a system app on mine called engineer mode. This reveals the actual file system as well as other info.
It appears there is not a reboot bootloader mode, it does have reboot recovery, but also I do not think it has fastmode. There is another mode called download mode, but I have not successfully used this for anything. Also, connecting usb abd in recovery mode yields device unauthorized.
If you are interested, I'll explain how I got frp partially bypassed. Added emergency contact, added an email, a prompt came up asking me which service to use, there were like four options like google, etc. I chose one I had not heard of that had the word executive, because it sounded official. When I chose it, another prompt came up saying that in order to use this service I had to set up a lock screen, make sure func is enabled. When I then turned the screen off and back on, I had a google search option from the lock screen. Pressed it and said "open settings", enabled install of unknown sources, used google search and said "open chrome". Used chrome to download quickshortcutmaker. Used google search and said "open file manager". Used file manager to install quickshortcutmaker. At this point I could have just used the phone from there, however... I added quickshortcutmaker to the func lock screen list by using google search to open settings. Then from the lock screen, I could launch quickshortcutmaker (or use google search). I then used quickshortcutmaker to run 'joy launcher' and voila, in. However, only the back button worked, and if I tried to log into google, it would bring up the frp lock screen. So, using the quickshortcutmaker, I ran every activity on the phone, and using the engineermode system app (I am pretty sure it was that one) I toggled an option called 'demo mode'. Upon exiting this system app and pressing the square button next to the home and back button, I saw an option to accept user agreement, or something like that. I scrolled down and checked the box, and voila, frp lock totally gone, and now I can log into google.
Now I am trying to root, but first I must unlock the bootloader.
Click to expand...
Click to collapse
You can use this guide for your phone:
https://forum.xda-developers.com/canvas-juice/how-to/guide-unlocking-bootloader-rooting-t3705781
HIT THANKS IF FOUND USEFUL
No, it does not work. I am having several issues. First, I cannot get adb windows drivers to recognize this device, I have installed every qualcomm driver I could find, also tried the universal adb drivers and even the drivers that come with the phone. Nothing works.
However, I have a rooted tablet with an otc cable that does connect via adb. However, adb reboot bootloader simply reboots the phone. There is a download mode, but I do not have fastboot installed on the tablet, so I cannot check if download mode = fastboot.
I am able to adb push files to /data/local/tmp and running adb shell chmod 755, I have succesfully unstalled busybox and can execute commands such as vi. The user is still not root, but I feel I am close.
I tried to download the emmc internal memory using backup qualcomm tool, but I seem to not have the correct drivers for my phone. My plan was to edit ro.debuggable to 1 and reflash, so I can adb root and remount as rw.
Best I can do so far
So far cracking it is still undone...but I can offer up some advice...download 3c, advanced tools and dev tools. A notepad++ would help too so you can re-create rom commands to make your own. Use advanced tools to look for vendor. Once there you should see a few files that make you question Google's business practices. Go into them to make alterations using dev toolds. The rest of the files can be re-made from scratch using notepad and 3c's rom manager.
This phone is complete garbage, I ended up giving it away because the touch screen would go to random spots on the phone randomly. It appears to be a cheap phone I do not like. Got an LG that as far superior.
I may have a Root method for the 5044R and the 5044C, I need someone with the 5044R and 5044C to get in contact with me. Best way to do that is Telegram. Here is the Link: https://t.me/Android_General_Chat
I'm currently Testing Root on the 5044C
---------- Post added at 12:56 AM ---------- Previous post was at 12:42 AM ----------
Alcatel 5044C and Alcatel 5044R PWND and Rooted. Doing 5044C TWRP Recovery now.
UPDATE: TWRP Ported and WORKING. Now somebody make some custom Roms.
I'll have a Custom Stock Rom out for this soonishly if anyone is interested
Alcatel Verso Root Solution
I have an Alcatel Verso (Yes, the Qualcomm 5044c) and the solution from PizzaG works well. The bootloader is unlocked and the phone is rooted. It works better now than when it was new. Thank you, PizzaG!
-
Tip: carefully follow the instructions, try different USB ports and unplug any other USB cables / devices. You will need MS Windows, the .mbn file and Sugar_QCT (from PizzaG).
Where is the root method?
I am just curious of the method used, I do not have this phone.
mrhealthpatriot said:
I have an Alcatel Verso (Yes, the Qualcomm 5044c) and yes, the solution from PizzaG actually works. The phone boots properly, has Magisk, etc. Thank you, PizzaG!
-
Tip: carefully follow the instructions, try different USB ports, unplug any other USB drives and be persistent.
You will need MS Windows and Sugar_QCT (from PizzaG). The phone is rooted, working and more responsive.
Click to expand...
Click to collapse
Of course it works, otherwise I wouldn't have posted it along with modified boot and TWRP. Unsure if I released the modified stock rom or not?
@PizzaG Could you describe the method briefly, or post a link to the method, I am not seeing it.
diorthotis said:
@PizzaG Could you describe the method briefly, or post a link to the method, I am not seeing it.
Click to expand...
Click to collapse
I use the Alcatel Internal flashing software. It grabs the firmware files from their servers. I then swap their boot image for my modified image and then use the software to flash the device. It's then rooted and you can install TWRP or swap recovery files in the Flasher software and it will flash for you. Device must be bootloader unlocked from the factory but they disabled fastboot.
Thank you, do you have a link for instructions on how you modified the boot files, and which ones?
diorthotis said:
Thank you, do you have a link for instructions on how you modified the boot files, and which ones?
Click to expand...
Click to collapse
Once the program downloads the firmware, I was able to get some good info from the flashing logs that told me what every file is. So I just grabbed the B file which is boot and ran it through magisk manager to patch it. Pretty easy peasy. TWRP I just ported from another msm8909 device. The TWRP for 5044C also woks for 5044R models as well as the whole rooting procedure. I would build some more recoveries for it from source but I don't have the device so I can't be bothered with that unless someone wants to donate towards the cause.
Verso Unlocking
This is basically how I unlocked the phone. First, I went into developer options and allowed "OEM Unlocking* and "USB Debugging." Then I opened Windows and downloaded the Actatel drivers. I also installed SugarQCT and the *.mbn file from PizzaG's website. Once Windows and ABD recognize the phone., I launch SugarQCT. I used the version from PizzaG, but said no to any update requests. (It crashed after it updated itself.). In SugarQCT, I started the phone firmware flash process and pasted the *. mbn file into the "5044c" folder that the program creates during flashing. It is important to overwrite the existing *.mbn while SugarQCT is downloading the firmware files so that the newly pasted version is flashed to the phone. Once it is done, SugarQCT deletes the entire temporary folder. When the "flashing completed" or "success" message pops up, just reboot the phone and set it up as usual. I used Flashify to flash Magisk to the recovery since PizzaG's ".mbn installs SuperSu.
mrhealthpatriot said:
This is basically how I unlocked the phone. First, I went into developer options and allowed "OEM Unlocking* and "USB Debugging." Then I opened Windows and downloaded the Actatel drivers. I also installed SugarQCT and the *.mbn file from PizzaG's website. Once Windows and ABD recognize the phone., I launch SugarQCT. I used the version from PizzaG, but said no to any update requests. (It crashed after it updated itself.). In SugarQCT, I started the phone firmware flash process and pasted the *. mbn file into the "5044c" folder that the program creates during flashing. It is important to overwrite the existing *.mbn while SugarQCT is downloading the firmware files so that the newly pasted version is flashed to the phone. Once it is done, SugarQCT deletes the entire temporary folder. When the "flashing completed" or "success" message pops up, just reboot the phone and set it up as usual. I used Flashify to flash Magisk to the recovery since PizzaG's ".mbn installs SuperSu.
Click to expand...
Click to collapse
oh, did I really do it with SuperSU? My bad on that. Seems weird I'd use that. But yep, nice job of explaining the procedure. You should be nice and post your magisk patched version of boot.img or pass it to me to further modify it and i'll post it on here. I'd like to make it selinux permissive and remove the line of code that reflashes stock recovery on reboot. If you used my original SuperSu patched image and then repatched it with Magisk, then it wouldn't need to be repatched for selinux and such.
Flashing Files
Actually, I didn't patch the boot image or modify any files. I used the 5044C_TWRP.img and BVT4H1H0CL10.mbn that you posted. I have an Alcatel rom from Needrom, but I didn't use that either. I flashed Magjsk.zip with flashify, but I could have flashed it via adb. SuperSu was already installed..