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!
Related
Hi all,
I recently got a new Dell Venue 7 3740 (yeah, not my first choice, but it was free for buying a computer). Anyway, started reading up on how to root the thing. I have a couple of apps that require root.
I found this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
and also the main Dell page: http://opensource.dell.com/releases/Venue_7_3740_Merrifield/developer-edition/
Following Dell's guide to rooting appears to NOT root it. Installing Root Checker confirms I don't have root. Unbricked it and got it back up from 4.4.2 to 4.4.4. By reading the first guide for the 3840, my question is ...
Is the boot image linked there compatible with my 3740?
(yeah, I know this should be in the developer section ... unfortunately I don't have enough posts ... also, I am familiar with rooting/flashing/etc, my first device that I put CM7 on was the original Galaxy S1 ... and I have CM10 on my S3.)
Tried, failed
Yeah I got this tablet with a PC too and tried rooting. It FUBAR'd on me and I had to wrestle with unbricking it. Which sorry to say is a job and a half, the images on Dell's site are corrupt for this WiFi only version (no partition.tbl file, system image incomplete). Ending up downloading the LTE versions firmware to get the missing files and rewriting the batch as the file names for the fastboot commands were wrong too. And even then the tablet wouldn't boot, so I had to store the OTA on an SD card and use recovery to flash it. Unfortunately that leaves me with 4.4.2 and the dreaded clock and browser issues. And OTA doesn't work, it keeps saying no updates are available. Spoke with a Dell rep who said OTAs were suspended and to try again in a week but I think OTA was broken for me when I tried rooting and boot loader was unlocked (which the PDF on Dell's site warns you about).
So now I have a working tablet that skips hours ahead and has general stability issues.
reaper-death said:
Yeah I got this tablet with a PC too and tried rooting. It FUBAR'd on me and I had to wrestle with unbricking it. Which sorry to say is a job and a half, the images on Dell's site are corrupt for this WiFi only version (no partition.tbl file, system image incomplete). Ending up downloading the LTE versions firmware to get the missing files and rewriting the batch as the file names for the fastboot commands were wrong too. And even then the tablet wouldn't boot, so I had to store the OTA on an SD card and use recovery to flash it. Unfortunately that leaves me with 4.4.2 and the dreaded clock and browser issues. And OTA doesn't work, it keeps saying no updates are available. Spoke with a Dell rep who said OTAs were suspended and to try again in a week but I think OTA was broken for me when I tried rooting and boot loader was unlocked (which the PDF on Dell's site warns you about).
So now I have a working tablet that skips hours ahead and has general stability issues.
Click to expand...
Click to collapse
Hmm ... Interestingly enough, I ran through the unbrick procedure from Dell, and didn't have any issues with it whatsoever. I'm not sure if they updated the TGZ since you updated.
I have read that root is for ADB to start with. Can anyone confirm this? If so, then which package could I get for a superuser binary?
ProfM2 said:
Hmm ... Interestingly enough, I ran through the unbrick procedure from Dell, and didn't have any issues with it whatsoever. I'm not sure if they updated the TGZ since you updated.
I have read that root is for ADB to start with. Can anyone confirm this? If so, then which package could I get for a superuser binary?
Click to expand...
Click to collapse
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Following the root process initially worked and the temp cwm recovery let me flash the supersu update. It booted with su just fine and I tried a couple apps that needed root and they worked. Once I rebooted again the tablet showed up with a USB icon and would go no further. Never having dealt with Intel SoC drivers it took me a while to get them installed properly, and then I eventually understood what "full power off" meant lol.
Do you know how I can relock the bootloader and get OTA working again, assuming I'm already on 4.4.2 from the OTA zip installed via recovery?
Thanks.
reaper-death said:
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Following the root process initially worked and the temp cwm recovery let me flash the supersu update. It booted with su just fine and I tried a couple apps that needed root and they worked. Once I rebooted again the tablet showed up with a USB icon and would go no further. Never having dealt with Intel SoC drivers it took me a while to get them installed properly, and then I eventually understood what "full power off" meant lol.
Do you know how I can relock the bootloader and get OTA working again, assuming I'm already on 4.4.2 from the OTA zip installed via recovery?
Thanks.
Click to expand...
Click to collapse
You better redo the unbrick procces cause as you are now, you won't be able to update your tablet and 4.4.2 has some issues with the clock and browser. The best way to root is by thetered cwm, I did it and it's working great.
reaper-death said:
I did this process just a couple days ago so everything I pulled from opensource.dell was current. The unbrick tgz on the site shows up as 128mb for the wifi only A1195 and the A5195 shows as 821mb (odd). When I extracted the tgz it said "unexpected end" or something like that on the system image. Then again when I extracted from that extracted tgz.
Click to expand...
Click to collapse
This is quite odd. From the documentation, it appears that the A195 is for the LTE version, and the A150 is Wifi only. Since I have the 3740 Wifi only, I only pulled the A150 version.
The Unbricking process was very straightforward and everything went smoothly, and after it rebooted, it prompted that there was a system update from Dell, and that took me from the 4.4.2 from the TGZ, to 4.4.4
ProfM2 said:
This is quite odd. From the documentation, it appears that the A195 is for the LTE version, and the A150 is Wifi only. Since I have the 3740 Wifi only, I only pulled the A150 version.
The Unbricking process was very straightforward and everything went smoothly, and after it rebooted, it prompted that there was a system update from Dell, and that took me from the 4.4.2 from the TGZ, to 4.4.4
Click to expand...
Click to collapse
http://opensource.dell.com/releases/Venue_7_3740_Merrifield/developer-edition/Doc/OSS_A150&A195.pdf
* For Wifi-only device on A150 and Wifi / LTE device on A195
I see it now, I think I was misinterpreting the above statement which means I've been flashing the A195 rom this whole time. Thank you all for your help! :good:
After getting my 3740 back to "Unbricked" mode, and OTA upgraded to 4.4.4, it appears that I'm completely locked out of the rooting process.
I've tried to start over with the Dell info (unlocking bootloader), however, neither of my PC's will detect the tablet when using xFSTK (one PC - Win8.1-64bit, other XP-32bit). The tablet IS detected, however, it appears that the drivers are no longer correct(?).
I normally run Ubuntu, and thats where my Android development setup is on ... I see that xFSTK is available for Linux ... has anyone used it? or would I be better trying to fight Windows?
ProfM2 said:
After getting my 3740 back to "Unbricked" mode, and OTA upgraded to 4.4.4, it appears that I'm completely locked out of the rooting process.
I've tried to start over with the Dell info (unlocking bootloader), however, neither of my PC's will detect the tablet when using xFSTK (one PC - Win8.1-64bit, other XP-32bit). The tablet IS detected, however, it appears that the drivers are no longer correct(?).
I normally run Ubuntu, and thats where my Android development setup is on ... I see that xFSTK is available for Linux ... has anyone used it? or would I be better trying to fight Windows?
Click to expand...
Click to collapse
It is mentioned somewhere that the 3740 and the 3840 use the same firmware. Assuming that, what you can do is download the latest SuperUser zip, copy it to the internal or external storage, then use THIS, or THIS to root through CWM.
graphdarnell said:
It is mentioned somewhere that the 3740 and the 3840 use the same firmware.
Click to expand...
Click to collapse
Hmmm ... I took this to mean that I could use the same boot.img as the Venue 8, and tried the process from this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
NOPE. (Don't try, it'll cause the tablet to go into the "help my androids' fallen and can't get up" icon. )
ProfM2 said:
Hmmm ... I took this to mean that I could use the same boot.img as the Venue 8, and tried the process from this thread: http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
NOPE. (Don't try, it'll cause the tablet to go into the "help my androids' fallen and can't get up" icon. )
Click to expand...
Click to collapse
I'm curious as to what it is you're trying to do. Why do you insist on having a developer's root (just the use of ADB shell), as opposed to full root flashing SuperSu from custom recovery?
graphdarnell said:
I'm curious as to what it is you're trying to do. Why do you insist on having a developer's root (just the use of ADB shell), as opposed to full root flashing SuperSu from custom recovery?
Click to expand...
Click to collapse
I just want full root.
Most of the info that I've read on here and elsewhere are geared to the 3830/3840. Not as much for the 3740. So, by playing with the device and learning what works/doesn't work, possibly others may find this info useful to them.
I've been having issues seeing the device from XP, Win8.1 and Ubuntu, in the 'off' state of the tablet, when the PC should be seeing the merrifield. Just this morning, after bricking it last night, I discovered that my PC seems to see the device right away if I press Vol+ while plugging in the microUSB. (again, something that may help someone else) I was planning on double checking this info later today, to make sure that it wasn't a fluke.
I do appreciate both of the links that you've posted in this thread, and I will check them out. Of course, both are labelled for the Venue 8, not the Venue 7 that I have. Since I've gained knowledge on the unbrick process I feel more comfortable trying them.
I've installed (or tried to install) SuperSU from the Play store, but it didn't appear to help much, since I didn't have the custom recovery setup at that time. I'll work on that tonight.
ProfM2 said:
I just want full root.
Most of the info that I've read on here and elsewhere are geared to the 3830/3840. Not as much for the 3740. So, by playing with the device and learning what works/doesn't work, possibly others may find this info useful to them.
I've been having issues seeing the device from XP, Win8.1 and Ubuntu, in the 'off' state of the tablet, when the PC should be seeing the merrifield. Just this morning, after bricking it last night, I discovered that my PC seems to see the device right away if I press Vol+ while plugging in the microUSB. (again, something that may help someone else) I was planning on double checking this info later today, to make sure that it wasn't a fluke.
I do appreciate both of the links that you've posted in this thread, and I will check them out. Of course, both are labelled for the Venue 8, not the Venue 7 that I have. Since I've gained knowledge on the unbrick process I feel more comfortable trying them.
I've installed (or tried to install) SuperSU from the Play store, but it didn't appear to help much, since I didn't have the custom recovery setup at that time. I'll work on that tonight.
Click to expand...
Click to collapse
A quick word on getting the device recognized in off mode, what worked for me was it needs to be completely powered off and nothing showing on the tablet screen then connect and bring up the device manager. Whatever shows up needs to be "Intel SoC" so change the driver to that if needed. When flashing firmware to unlock the bootloader the device's boot screen will show an "Intel Inside" logo instead of the normal "Dell" logo. I ended up running xFSTK commands in advance (they'll wait) and then running over to hook up the tablet (powered off) via USB as for some reason it'll show up and then I hear "da-Dunk" in Windows (device disconnected) after a short while which interrupts the process (same with fastboot commands). This was the unbrick process in a nutshell for me and I'm leaving it now as is (OTA'd to 4.4.4) until hopefully the supposed update to Lollipop comes around and maybe some progress is made on rooting it.
Hope this helps you!
reaper-death said:
A quick word on getting the device recognized in off mode, what worked for me was it needs to be completely powered off and nothing showing on the tablet screen then connect and bring up the device manager. Whatever shows up needs to be "Intel SoC" so change the driver to that if needed. When flashing firmware to unlock the bootloader the device's boot screen will show an "Intel Inside" logo instead of the normal "Dell" logo. I ended up running xFSTK commands in advance (they'll wait) and then running over to hook up the tablet (powered off) via USB as for some reason it'll show up and then I hear "da-Dunk" in Windows (device disconnected) after a short while which interrupts the process (same with fastboot commands). This was the unbrick process in a nutshell for me and I'm leaving it now as is (OTA'd to 4.4.4) until hopefully the supposed update to Lollipop comes around and maybe some progress is made on rooting it.
Hope this helps you!
Click to expand...
Click to collapse
I have finally settled down and got the tablet rooted. What's really odd, was Win8.1 kept losing the proper driver. I'm not sure exactly why ... but suffice it to say, I got it working. It did appear to be more stable when I hit the Vol+ and plugged in the USB, but then again it may have been a coincidence.
Open source dell
If you follow the link to dell open source, they do have a detailed PDF download for unlocking the boot loader etc. The file was too large for me to upload on XDA. I just found it today while I was researching how to root this tablet. I have not had a chance to try it yet.
http://opensource.dell.com/
That doesnt work for 3740 lte. I;ve done everything that was in PDF. OTA image should be with unlocker bootloader and root but its not. ;/
Its adb root not su big difference
Does anyone have any idea to root dell venue 7 3740 lte
The open source is for venue 7 3740 wifi
how can i hard reset this device please tell me.
Mahisasur said:
how can i hard reset this device please tell me.
Click to expand...
Click to collapse
Reset any android tbalet with ...
Setting >>>>> Backup & Reset >>>>> Factory Data Reset >>>>> Reset Tablet >>> Erase Everything
So, I was sort of thinking that at least rooting and OTA blocking with the handy hdx toolkit would be easy but I don't get the impression that it is working. My Firmware is 13.3.2.3.2 and I used towelroot via the toolkit. This is what I see when I root. (aren't allowed to post links/images yet so it's only a non-clickable link to the image, sorry)
i.imgur.com/GLtVd1R.jpg
As you can see, there are some error messages. It also asks me to select 'make it rain' but there is nothing on my device to actually select and it continues on without my input. It then says 'please wait until device reboots' but my device continues to be entirely unimpressed and doesn't reboot, not even a bit. In short, while the root *appears* to be doing something, I don't think it actually does because it can't find the stuff it needs. On the next screen it checks if the rooting worked but it only gets me another error message saying /system/bin/sh: su: not found
help, please?
You can download and install towelroot manually.
As for OTA updates, you can rename /system/etc/security/otacerts.zip to anything else (i.e. otacerts.zip.bak); that should block them.
I couldn't leave well enough alone despite @EncryptedCurse excellent advice and managed to troubleshoot it and get it working in the toolkit after all. In case someone has similar troubles (Error 2 and Error 3 are what I got at different times) here's how I got it working (in Windows 7):
-In the device manager I uninstalled the adb driver (with adb enabled the kindle is listed twice in the device manager, you should unistall the drivers of the one that *isn't* listed under portable devices) and restarted the computer. Edit: On second thought: I'm not sure if that uninstall worked. I think I needed to use uninstaller.exe in C:\Program Files (x86)\Amazon.com\Kindle Fire\Drivers to really remove the driver.
-Then I disabled ADB in the kindle. I also shut down my antivirus (not sure if it made a difference but some people have reported interference). Then I used the toolkit to install adb drivers again (in the instructions there it says to have adb enabled while doing this but if you get error messages while rooting try it this way.).
-Now I rebooted the computer again (this is important), checked that antivirus was still activated, checked that Bluestacks was *also* still shut down (having it or another emulator open leads to a complete different error message, I have learned ) and tried rooting with the toolkit again. It worked with no troubles.
The definite guide to rooting Samsung Galaxy J3(2016) SM-J320FN & FRP Locked Bootloop
As first I have to say, I had to create a thread in Q&A because of the low rank, but I am sure this can be moved to the J3 section as there are many questions on how to gain root access to this device. This guide can work on the SM-J320F model as well, but it hasn't been tested on other models, so don't try it !
Lets start :
Dont forget to Backup all your data before the process !!!
1. Tick USB Debugging and OEM Unlock in Developer Mode (OEM has to be ticked to unlock the bootloader)
2. Connect to PC with USB Cable and open Odin
3. Power off and reboot into Download Mode (VOL.DOWN+HOME+POWER)
4. Add twrp.zip to AP tab
5. Untick Auto-Reboot and Start
6. Wait to finish
7. When it's finished hold (VOL.DOWN+VOL.UP+HOME+POWER) to Power Off
8. Load into TWRP Mode (VOL.UP+HOME+POWER)
9. In TWRP first go to the Wipe Tab, check Cache and Data and click Wipe
10. Copy SuperSU into internal memory from your PC
11. Go back to TWRP and select Install, select the SuperSU from the internal memory and click install without ticking anything, then reboot
12. Wait for the phone to reboot, it may boot-loop a few times, and it boots slowly but dont interrupt the process !
13. From there on, check the root status by downloading Root Checker from PlayStore
KEEP OEM-UNLOCK ON ALL THE TIME, IF YOU DONT WANNA END UP WITH A BRICKED DEVICE(CUSTOM BINARY WAS BLOCKED BY FRP LOCK)!!!
If that happens, here is an official guide from the Samsung Kies Support Page :
IMPORTANT: You may need your device model name, S/N number, or IMEI number in order to proceed. This information can be found on the label underneath your device battery.
WARNING: This process permanently deletes all personal information from the device. The information will not be recoverable if you proceed with this process.
1. Open Kies 3 and click Tools > Firmware Upgrade and Initialization.
2. Enter your device Model name and click OK.
3. Enter the device S / N number and click OK.
4. Kies 3 will verify that the feature is available for your device. If the feature is available, click OK to continue.
5. The firmware version is displayed along with a note that the information on your device will be permanently deleted during this process. Click OK to continue.
6. Follow the steps to prepare your device for emergency recovery. Mark the checkbox next to I have read all of the above information. Select whether you agree to share this update with Samsung. Connect your device to Kies when you have activated the download mode. When your device is in download mode and connected to Kies 3, the Start upgrade button is available. Click Start upgrade to reinstall the firmware.
7. Touch Create backup to create a copy of selected items before proceeding. Touch Skip backup to proceed without backing up any items.
8. Kies 3 will download and prepare your system to update the firmware. This process can take some time. The time will vary based on your network and computer capabilities.
9. Respond to any security warnings about installing software.
10. The progress screen is shown during the upgrade process. The process will take several minutes to complete. Do not disconnect your device, turn the device off, or turn off your computer during this process.
11. Click OK when the upgrade is finished.
Therefore I provide you all the needed files to do this :
How to root SM-J320FN.rar
Works like a charm on J320FN.
I signed up just to say, after hours of trying different guides, accidentally factory resetting once or twice, and getting my phone stuck in a boot loop, this method worked. BUT it did factory reset my phone, but that's fine I've everything backed up and it wont take long to get it back. Maybe I pressed something I shouldn't have.
Some info on my phone in case it helps anyone in a similar position to how I was:
At one point I installed stock firmware from to get my phone out of the boot loop, I can't link it but if you google "J320FNXXU0APB4_J320FNO2C0APC1_O2C" (WITH quotes) you should find the page.
After doing that:
Android version: 5.1.1
Model number: SM-J320FN
Kernel version: 3.10.65-7225942 (Sun Feb 14 2016)
Build no: LMY47V.J320FNXXU0APB4
Baseband version: J320FNXXU0APB5
I hope I typed all that right. Thank you so much!!
have anyone tried on j320v?
kekambas18 said:
have anyone tried on j320v?
Click to expand...
Click to collapse
Going to attempt that right now wish me luck.
---------- Post added at 08:06 PM ---------- Previous post was at 07:09 PM ----------
And it didn't work. Not suprised, but I at least tried.
GN9166 said:
4. Add twrp.zip to AP tab
10. Copy SuperSU into internal memory from your PC
Click to expand...
Click to collapse
Hey, why this guide doesn't mention that I have to download something. It's definitely NOT definitive! What is twrp.zip? Where do I take it from? What is AP tab? Where exactly do I copy SuperSU? What will happen in the download mode?
Problems in Root J320AZ
My name is Dario Lobos. I am working as a gardener and I am making a little application in my phone. I don't have computer so I did it in Java n-ide. I started with a Samsung core prime but the screen was broken and I did change it and the technicians broke it and gave me an Samsung s320. Android 6 (api23) and after that the java n-ide don't compiles the permits that I am requesting in the manifest so I can't grant permissions to my apk. Parallel of it the phone always show a notice unauthorized actions have been made please restart the phone to undo the unauthorized actions. And the lookout said message root access detected. I wrote Samsung without any positive answer. No technical assistance at all. But the roots checkers says that I have no root in my phone. Now I am trying to do a root. But I don't know if someone have a hidden root access in my phone. A page suggest Framaroot and you suggest kingroot. I don't want to store all my phone in their server to root it. Does any program that don't access to all the data to root the phone?. I am writing you since you have more experience to request you if it is in your possibilities. Also to ask you about prompt root commands. Where I can find info about that. A suggestion to solve my problem. My simple all is here
....github.com/DarioLobos/sistemariego
....github.com/tranleduy2000/javaide/issues/163
....1drv.ms/u/s!Asr3Ewn45KOLtGOqDkoMq20A-hbc?e=24Wwx3
The system don't let me put url since I am new add please http...
Well thank you in advance and any help is wellcome
Regards,
Dario Lobos
Adding more information to what I did to try to find a an answer. I tried to root with Frama root 1.9.3 and the installation only request me access to the camera and after installed the programs showed a banner that said can't root your device.
Today I downloaded from firmware.mobi some zip and img files but I already I couldn't learn how to use them properly.
I am trying to avoid the exploids system because maybe is a hacker in the middle. Always I am trying to root w/o SIM card and with Wi-Fi off. So I think that kingroot and kingoroot are not useful for my.
I am trying to buy an old desktop computer as an alternative.
Well any suggestion is usefull and wellcome.
Before of all of that I did two factory reset in recovery mode.
Then I installed an apk Dev Tools (trinea) and one menu request me developer permit in accesibility setting. The phone started to change the color of the screen and the outside padding start to flashing red. Then was open a setting menu and the language was changed suddenly to Japanese or Korean while the screen was lighting like receiving knoks. I turned of the phone and restarted and hopefully I remembered the position in settings to change the language.
After that I had to use an apk repair system and fix Android and the screen get better but the padding outside still flashing in red ones in a while.
Also where added plenty sha certificates (settings user certificates) like system certificates
Go daddy
VeriSign
Some governments (Turkish, Spain, Japan, Germany, Holland, and more)
The Catholic religion with 6 certificates called
Quo Basis
And much more.
So I did another factory reset recovery mode. And the screen problem disappeared and the certificates that I turned off manually firt too (All) but the root alert in the look out and the security notice didn't disappeared.
Today I wanted to print your forum page and the phone put error. Only put error in your forum page.
Other thing that I had to to just after the unpackage the restored Android is disable the setup and transfer. Because I think that is this apk that were using to access and modify my files and grants permissions.
I installed the TWRP application but said the phone have no root.
Today I opened the developer option in settings and turned to on the OEM option to unlock the boot loader but instead of put a banner saying that all data will be erased put a banner saying that the device protection will be not work and didn't do the reboot or nothing more that put this dialog.
Dario Lobos
great, unlocken/rooten worked here. But after that, the mobile became unusable. All google apps complain no connection is available. I cannot update google play store, cannot update other google apps like youtube, or install any app now.
And perhaps it does not have anything to do with the mentioned process, but before I started the process, I made sure all nessacary file were on the sd card. But now I have finished wiping the data / cache from the recovery and all files on the sd card are gone.
I cannot login to google photos to see if the apps are backupped because every google app complains no internet connection is available.
So yes, rooting/unlocking worked, but that's the only thing that worked here. I now got a useless Samsung J3 2016...
I need assistant trying to root my J320FN, which I mistakenly wipe some backed up recovery file now, I can not get through with the rooting and I can get back to forma phone setting am locked up , samsung phone not coming up again please what can I do ?
GN9166 said:
The definite guide to rooting Samsung Galaxy J3(2016) SM-J320FN & FRP Locked Bootloop
As first I have to say, I had to create a thread in Q&A because of the low rank, but I am sure this can be moved to the J3 section as there are many questions on how to gain root access to this device. This guide can work on the SM-J320F model as well, but it hasn't been tested on other models, so don't try it !
Lets start :
Dont forget to Backup all your data before the process !!!
1. Tick USB Debugging and OEM Unlock in Developer Mode (OEM has to be ticked to unlock the bootloader)
2. Connect to PC with USB Cable and open Odin
3. Power off and reboot into Download Mode (VOL.DOWN+HOME+POWER)
4. Add twrp.zip to AP tab
5. Untick Auto-Reboot and Start
6. Wait to finish
7. When it's finished hold (VOL.DOWN+VOL.UP+HOME+POWER) to Power Off
8. Load into TWRP Mode (VOL.UP+HOME+POWER)
9. In TWRP first go to the Wipe Tab, check Cache and Data and click Wipe
10. Copy SuperSU into internal memory from your PC
11. Go back to TWRP and select Install, select the SuperSU from the internal memory and click install without ticking anything, then reboot
12. Wait for the phone to reboot, it may boot-loop a few times, and it boots slowly but dont interrupt the process !
13. From there on, check the root status by downloading Root Checker from PlayStore
KEEP OEM-UNLOCK ON ALL THE TIME, IF YOU DONT WANNA END UP WITH A BRICKED DEVICE(CUSTOM BINARY WAS BLOCKED BY FRP LOCK)!!!
If that happens, here is an official guide from the Samsung Kies Support Page :
IMPORTANT: You may need your device model name, S/N number, or IMEI number in order to proceed. This information can be found on the label underneath your device battery.
WARNING: This process permanently deletes all personal information from the device. The information will not be recoverable if you proceed with this process.
1. Open Kies 3 and click Tools > Firmware Upgrade and Initialization.
2. Enter your device Model name and click OK.
3. Enter the device S / N number and click OK.
4. Kies 3 will verify that the feature is available for your device. If the feature is available, click OK to continue.
5. The firmware version is displayed along with a note that the information on your device will be permanently deleted during this process. Click OK to continue.
6. Follow the steps to prepare your device for emergency recovery. Mark the checkbox next to I have read all of the above information. Select whether you agree to share this update with Samsung. Connect your device to Kies when you have activated the download mode. When your device is in download mode and connected to Kies 3, the Start upgrade button is available. Click Start upgrade to reinstall the firmware.
7. Touch Create backup to create a copy of selected items before proceeding. Touch Skip backup to proceed without backing up any items.
8. Kies 3 will download and prepare your system to update the firmware. This process can take some time. The time will vary based on your network and computer capabilities.
9. Respond to any security warnings about installing software.
10. The progress screen is shown during the upgrade process. The process will take several minutes to complete. Do not disconnect your device, turn the device off, or turn off your computer during this process.
11. Click OK when the upgrade is finished.
Therefore I provide you all the needed files to do this :
How to root SM-J320FN.rar
Click to expand...
Click to collapse
The link says "the key is invalid"
Hello, all!
I've been running Nexus v4.0.5 on my Thor device for a couple of years, but I'm more than ready for an upgrade. An upgrade to CM 14.1/LineageOS, to be exact.
At this point, I have a rooted Thor device with Safestrap v4.0.1 installed; Nexus v4.0.5 is installed in the STOCK ROM slot.
From what I understand, I need to unlock my boot loader, install TWRP, and then... something. Can anyone tell me how to go about unlocking my bootloader, installing TWRP, and doing everything else necessary to get CM 14.1 installed?
Oh, and if you're wondering exactly what I've done to this device thus far, check out this guide I made a few years ago. I've done all the steps outlined therein.
Thanks!
Rvby1 said:
Hello, all!
I've been running Nexus v4.0.5 on my Thor device for a couple of years, but I'm more than ready for an upgrade. An upgrade to CM 14.1/LineageOS, to be exact.
At this point, I have a rooted Thor device with Safestrap v4.0.1 installed; Nexus v4.0.5 is installed in the STOCK ROM slot.
From what I understand, I need to unlock my boot loader, install TWRP, and then... something. Can anyone tell me how to go about unlocking my bootloader, installing TWRP, and doing everything else necessary to get CM 14.1 installed?
Oh, and if you're wondering exactly what I've done to this device thus far, check out this guide I made a few years ago. I've done all the steps outlined therein.
Thanks!
Click to expand...
Click to collapse
See below; same steps apply. You do not need to remove SafeStrap or Nexus. Note all data will be lost; be sure to backup any important content.
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post72472618
Davey126 said:
See below; same steps apply. You do not need to remove SafeStrap or Nexus. Note all data will be lost; be sure to backup any important content.
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post72472618
Click to expand...
Click to collapse
I've gotten to the point where I need to upgrade TWRP to the latest version, but I can't seem to get fastboot to recognize the TWRP file.
I'm using the command
fastboot -i 0x1949 flash recovery thor-twrp-3.1.1-1
thor-twrp-3.1.1-1 is in platform-tools, and that's the directory I'm running these commands in.
Do you know what I'm doing wrong?
Thanks!
Rvby1 said:
I've gotten to the point where I need to upgrade TWRP to the latest version, but I can't seem to get fastboot to recognize the TWRP file.
I'm using the command
fastboot -i 0x1949 flash recovery thor-twrp-3.1.1-1
thor-twrp-3.1.1-1 is in platform-tools, and that's the directory I'm running these commands in.
Do you know what I'm doing wrong?
Thanks!
Click to expand...
Click to collapse
File ID appears to be incorrect; should be: thor-twrp-3.1.1-1.img
Davey126 said:
File ID appears to be incorrect; should be: thor-twrp-3.1.1-1.img
Click to expand...
Click to collapse
Hah, yeah, that's it. Totally forgot about file extensions.
So, I've gotten TWRP flashed, and I've flashed LineageOS and GAPPS according to the instructions here. When I try to boot up, though, I get stuck on the "Welcome to your Kindle Fire HDX" screen; it gives me the option to restore data from a previous device or start fresh. Since I don't have an internet connection on my device, I can't do anything related to my prior devices. And clicking on the start fresh option crashes the start-up program and sends be back to the language selection screen (which pops up just before the "Welcome to your Kindle Fire HDX" screen).
Now, before I flashed GAPPS, I didn't have this problem. The "Welcome to your Kindle Fire HDX" screen didn't show up, so I was able to set-up the OS and use it.
I've tried wiping the device, restarting, and reflashing LineageOS and GAPPS (both in a queue and one after another).
Any idea what's going on?
Rvby1 said:
Hah, yeah, that's it. Totally forgot about file extensions.
So, I've gotten TWRP flashed, and I've flashed LineageOS and GAPPS according to the instructions here. When I try to boot up, though, I get stuck on the "Welcome to your Kindle Fire HDX" screen; it gives me the option to restore data from a previous device or start fresh. Since I don't have an internet connection on my device, I can't do anything related to my prior devices. And clicking on the start fresh option crashes the start-up program and sends be back to the language selection screen (which pops up just before the "Welcome to your Kindle Fire HDX" screen).
Now, before I flashed GAPPS, I didn't have this problem. The "Welcome to your Kindle Fire HDX" screen didn't show up, so I was able to set-up the OS and use it.
I've tried wiping the device, restarting, and reflashing LineageOS and GAPPS (both in a queue and one after another).
Any idea what's going on?
Click to expand...
Click to collapse
- insure bootloader is unlocked; unlock again if uncertain
- be sure to wipe system & data partitions before flashing LinOS
- ROM and GAaps (7.1/arm/nano) should be flashed in one operation
- if still no joy downgrade to TWRP 3.0.0-1 then try again
- as a last resort flash Fire Nexus KTU84Q (just one file), boot and allow ROM to initialize, then return to TWRP and reflash LinOS + GAaps
The above may seem a bit random but there's a reason behind each suggestion and the order in which they are presented.
Davey126 said:
- insure bootloader is unlocked; unlock again if uncertain
- be sure to wipe system & data partitions before flashing LinOS
- ROM and GAaps (7.1/arm/nano) should be flashed in one operation
- if still no joy downgrade to TWRP 3.0.0-1 then try again
- as a last resort flash Fire Nexus KTU84Q (just one file), boot and allow ROM to initialize, then return to TWRP and reflash LinOS + GAaps
The above may seem a bit random but there's a reason behind each suggestion and the order in which they are presented.
Click to expand...
Click to collapse
So, I can't seem to get fastboot to run unlock because fastboot isn't recognizing my kindle as a device. When I go to Device Manager, my Kindle is under Portable Devices, and if I browse for drivers on my computer, I only get "MTB USB Device."
Any advice?
Rvby1 said:
So, I can't seem to get fastboot to run unlock because fastboot isn't recognizing my kindle as a device. When I go to Device Manager, my Kindle is under Portable Devices, and if I browse for drivers on my computer, I only get "MTB USB Device."
Click to expand...
Click to collapse
- download drivers from this post (prequisite section); unzip as needed
- open windows device manager
- tether device in fastboot mode
- take note of entries added; delete those devices
- remove tether and reattach (might have to reboot one/both devices)
- when Windows prompts for drivers direct it to those downloaded
Davey126 said:
- download drivers from this post (prequisite section); unzip as needed
- open windows device manager
- tether device in fastboot mode
- take note of entries added; delete those devices
- remove tether and reattach (might have to reboot one/both devices)
- when Windows prompts for drivers direct it to those downloaded
Click to expand...
Click to collapse
So, I can't seem to get into fastboot mode. I don't have a factory cable, and none of the commands listed here activate fastboot mode.
What should I do?
Sorry for my ignorance!
Rvby1 said:
So, I can't seem to get into fastboot mode. I don't have a factory cable, and none of the commands listed here activate fastboot mode.
What should I do?
Sorry for my ignorance!
Click to expand...
Click to collapse
We are all ignorant about 99.99% percent of the world around us with unique 'points of light' distinguishing various individuals; never apologize for being ignorant!
Possible solution:
- boot into TWRP (turn off tablet then restart by pressing <power>+<vol-down> together; release first logo appears)
- tether device to host PC (assumes Windows)
- tap Reboot
- tab Bootloader
Above sequence should place your tablet in 'fastboot mode'. If the word 'Ready' appears on the tablet screen the correct drivers are installed on the PC. If not follow previously posted procedure for updating drivers.
Davey126 said:
We are all ignorant about 99.99% percent of the world around us with unique 'points of light' distinguishing various individuals; never apologize for being ignorant!
Possible solution:
- boot into TWRP (turn off tablet then restart by pressing <power>+<vol-down> together; release first logo appears)
- tether device to host PC (assumes Windows)
- tap Reboot
- tab Bootloader
Above sequence should place your tablet in 'fastboot mode'. If the word 'Ready' appears on the tablet screen the correct drivers are installed on the PC. If not follow previously posted procedure for updating drivers.
Click to expand...
Click to collapse
True, true! Thanks for your kind words, Davey!
And thanks for your help with this, too!
I was able to boot into fast mode, and I went through the unlock process again. With that done, I tried to reflash LineageOS and GAPPS, but I ran into the same issue I did before. So I did a bit of googling (which I didn't exactly think to do before :C), and apparently this is a known issue for CM operating systems.
Here's the fix.
Swipe down (a few hundred times) to get the notification tray. Go to settings. Turn on wifi. Problem (probably) solved.
Thanks again for all your help, Davey! I wouldn't have gotten Nexus running back in the day without ya, and I wouldn't be running LineageOS right now if you hadn't been my savior a second time around. And in addition to my thanks, sorry for not googling first! It would have saved both of us a bit of trouble, haha.
Rvby1 said:
True, true! Thanks for your kind words, Davey!
And thanks for your help with this, too!
I was able to boot into fast mode, and I went through the unlock process again. With that done, I tried to reflash LineageOS and GAPPS, but I ran into the same issue I did before. So I did a bit of googling (which I didn't exactly think to do before :C), and apparently this is a known issue for CM operating systems.
Here's the fix.
Swipe down (a few hundred times) to get the notification tray. Go to settings. Turn on wifi. Problem (probably) solved.
Thanks again for all your help, Davey! I wouldn't have gotten Nexus running back in the day without ya, and I wouldn't be running LineageOS right now if you hadn't been my savior a second time around. And in addition to my thanks, sorry for not googling first! It would have saved both of us a bit of trouble, haha.
Click to expand...
Click to collapse
Hey - glad you got it working and left a solution that hopefully will help others who encounter the same issue. Enjoy your rejuvenated device!
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..