Related
I'm having problems updating the OS on my unrooted, stock Nexus S I9020A, running on Straight Talk on an AT&T sim. When I purchased it, it was on 2.3.4. As soon as I turned it on (which was prior to the release ICS for this phone), it upgraded itself to 2.3.6 over WiFi via an OTA download. However when ICS came out, it did not upgrade itself OTA, despite waiting several weeks after the OTA appeared to be rolling out here in the US (since I got the 2.3.6 upgrade before I had even put the sim in, I assumed that the fact that I was on Straight Talk should not matter, but I'm not 100% clear on that). In any event, after getting tired of waiting, I updated the OS to ICS 4.0.4 manually by downloading the official OTA zip file manually, copying it to the phone, rebooting into recovery mode, and applying the update. Now that JB has been released, I've waited again for it to update automatically OTA, but no joy. So I again downloaded the official OTA zip file (android.clients.google.com/pa...a/P2lZDQWb.zip), and tried to do it manually. This time, however, I get the following error each time:
Finding update package . . .
Opening update package . . .
Verifying update package . . .
Installing update . . .
Verifying current system . . .
assert failed: apply_patch_space (16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted
As far as I can tell, I'm using the correct file. Currently, from the bootloader my Product Name is Herring; Hardware Version is Rev. 16; Bootloader is ver. I9020XXKL1; Baseband Ver. is I9020UCKJ1; and Carrier Info is AT&T. In Settings, About Phone, it says my baseband is I9020AUCKJ1, and Kernel is 3.0.8-g665123, [email protected] #1, Thus. Feb 2 16:56:02 PST 2012.
I've also tried doing a full reset on the phone, but that doesn't help. Asking it to check for updates doesn't do anything, and I get the same error message when I tried to do it manually as described above after resetting.
Any advice? Hate to be stuck on ICS. Many thanks.
DavRoc said:
I'm having problems updating the OS on my unrooted, stock Nexus S I9020A, running on Straight Talk on an AT&T sim. When I purchased it, it was on 2.3.4. As soon as I turned it on (which was prior to the release ICS for this phone), it upgraded itself to 2.3.6 over WiFi via an OTA download. However when ICS came out, it did not upgrade itself OTA, despite waiting several weeks after the OTA appeared to be rolling out here in the US (since I got the 2.3.6 upgrade before I had even put the sim in, I assumed that the fact that I was on Straight Talk should not matter, but I'm not 100% clear on that). In any event, after getting tired of waiting, I updated the OS to ICS 4.0.4 manually by downloading the official OTA zip file manually, copying it to the phone, rebooting into recovery mode, and applying the update. Now that JB has been released, I've waited again for it to update automatically OTA, but no joy. So I again downloaded the official OTA zip file (android.clients.google.com/pa...a/P2lZDQWb.zip), and tried to do it manually. This time, however, I get the following error each time:
Finding update package . . .
Opening update package . . .
Verifying update package . . .
Installing update . . .
Verifying current system . . .
assert failed: apply_patch_space (16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted
As far as I can tell, I'm using the correct file. Currently, from the bootloader my Product Name is Herring; Hardware Version is Rev. 16; Bootloader is ver. I9020XXKL1; Baseband Ver. is I9020UCKJ1; and Carrier Info is AT&T. In Settings, About Phone, it says my baseband is I9020AUCKJ1, and Kernel is 3.0.8-g665123, [email protected] #1, Thus. Feb 2 16:56:02 PST 2012.
I've also tried doing a full reset on the phone, but that doesn't help. Asking it to check for updates doesn't do anything, and I get the same error message when I tried to do it manually as described above after resetting.
Any advice? Hate to be stuck on ICS. Many thanks.
Click to expand...
Click to collapse
The patch you are trying to apply fails pre-requisite system check. Probably the wrong version.
Go to https://developers.google.com/android/nexus/images#sojuajzo54k, or get this full Google Factory Image, un-tar/7-zip and run flash-all.bat or flash-all.sh (linux).
Check this out for steps in detail.
Thanks. That's what I thought. And I thought the solution was what you suggested, but I'm afraid it feels over my head. I've been looking for more detailed instructions for someone at my skill level, but have not found them.
I see that the 1st step of the more detailed instructions is to download the Android SDK Tools, but the instructions are written for the Windows tools, and I'm on a Mac. I see that there appears to be a Mac version at developer.android.com/sdk/index.html. However that version appears to be for 64 bit systems, and my old Mini is a 32 bit (running 10.6.8), and, indeed, when I try to run Eclipse (which is what I gather is the program that allows access to the other tools), it says its not compatible with my system. While there doesn't appear to be a 32 bit version of the ADT bundle, I see that there's also a download link for "SDK Tools Only." I'm not clear if that's 32 bit.
So I'm stuck on step one, much less understanding how actually run SDK Manager, and where to put the factory image on a Mac system, and how to issue the linux commands to the phone (I'm guessing that once I'm running the right program on my Mac when I connect the phone via USB I can issue the commands).
So, any idea where there are detailed instructions for doing this on a Mac?
Many thanks.
UPDATE: Never mind, I figured it out. Your answer gave me the phrases to google.
Thought I'd post what worked for me in case it helps others, since I didn't find any tutorials that actually had all steps or all instructions accurate.
I more or less followed the instructions at forum.xda-developers.com/showthread.php?t=1917237 (can't post full links yet, so add the necessary http:// prefix to all links) to download and install ADB and fastboot on a Mac. But you don't need the full ADT Bundle (which is 64 bit so won't work on older Macs). If you scroll down to Download for Other Platforms, you can download the SDK only (I saw on other sites links to download just ADB and fastboot, but wanted to get my stuff directly from Google), and that worked on my 32 bit system. The instructions at the link above about what files you need, and where to put them worked for me (you can put your Android folder as described there anywhere). Key seems to be to have ADB and fastboot in the same directory as the unpacked factory image files that you'll also download. I did not bother with the nano editor steps (because I didn't fully understand what they were doing, and they turned out to be completely unnecessary).
Here's another set of instructions for getting ADB and fastboot only, but I didn't use these: android.stackexchange.com/questions/26612/doing-a-clean-install-of-android-on-nexus-s-galaxy-nexus-or-nexus-7.
I also downloaded the latest factory image from developers.google.com/android/nexus/images (see not above about placement of files).
I then put the phone is USB Debug mode in Settings/Developer Options/USB Debugging.
I then went into fastboot mode by turning off the phone, then press and hold Volume Up, then press and hold Power.
I then more or less followed the step by step instructions here: forums.androidcentral.com/nexus-4-rooting-roms-hacks/223923-guide-nexus-4-factory-image-restore.html, substituting the directories I had created with the downloads above, and the files I had downloaded (these instructions are for a Nexus 4). You'll note, however, that the factory image has batch and shell files with instructions that match those given, and you can see those instructions by opening the bat files or sh files with a text editor. None of the batch or shell files would execute for me though, so I had to do the steps manually as outlined in the link above. Also, the instructions at the link say that for Macs you have to add "-mac" (without the quotes) to each Linus command. That didn't work for me, and I just used the commands as written. I preceded all commands with ./ after having first using the ./ cd command to get to the right directory where the files were located, as noted above. Finallly, Instead of step 5, I did the command ./ fastboot oem unlock.
Hopefully this will help someone else.
This is a guide to upgrade Nextbook Ares 8, disable encryption, and flash permanent TWRP recovery to device.
Walmart is selling the Nextbook Ares 8 for $62.52
This rom works great, and sound is now back to normal, on other roms sound worked but was very low.
https://www.walmart.com/ip/Nextbook-Ares-8-Tablet-16GB-Quad-Core/43267399
To use, download ares8_5.0_upgrade_5.1.zip, extract and run either Linux script or Windows batch file.
Bootloader must be unlocked
fastboot/adb must be installed system wide and working.
make sure scripts are set to executable
connect tablet to pc, leave connected until tablet reboots and is ready to set up
open terminal in folder where you extracted ares8_5.0_upgrade_5.1.zip
open cmd window where you extracted ares8_5.0_upgrade_5.1.zip
Linux
Code:
adb reboot bootloader
./fastboot.sh
Windows
Code:
adb reboot bootloader
fastboot_cmd.bat
That's it, takes a few minutes to install, leave connected to pc, when completed tablet will reboot to setup screen, setup and enjoy.
Download
https://www.androidfilehost.com/?fid=745425885120720323
Credits
@N810E
@zefie
@vampirefo
vampirefo said:
This is a guide to upgrade Nextbook Ares 8, disable encryption, and flash permanent TWRP recovery to device.
Walmart is selling the Nextbook Ares 8 for $62.52
This rom works great, and sound is now back to normal, on other roms sound worked but was very low.
https://www.walmart.com/ip/Nextbook-Ares-8-Tablet-16GB-Quad-Core/43267399
To use, download ares8_5.0_upgrade_5.1.zip, extract and run either Linux script or Windows batch file.
Bootloader must be unlocked
fastboot/adb must be installed system wide and working.
make sure scripts are set to executable
connect tablet to pc, leave connected until tablet reboots and is ready to set up
open terminal in folder where you extracted ares8_5.0_upgrade_5.1.zip
open cmd window where you extracted ares8_5.0_upgrade_5.1.zip
Linux
Code:
adb reboot bootloader
./fastboot.sh
Windows
Code:
adb reboot bootloader
fastboot_cmd.bat
That's it, takes a few minutes to install, leave connected to pc, when completed tablet will reboot to setup screen, setup and enjoy.
Download
https://www.androidfilehost.com/?fid=745425885120720323
Credits
@N810E
@zefie
@vampirefo
Click to expand...
Click to collapse
@vampirefo and others who contributed, this is the best rom for this 5.0 device yet. At 8 hrs. unplugged, in deep sleep, I had 98% battery left. The interactive governor deep sleep offline bug is gone. The power disconnecting, reconnecting on charge is gone also. The only issue I have noticed, so far, is that the wifi connection logo at the top is not always showing as full or 100%. That is despite being inches from my router. Furthermore, when I use mixplorer, totalcommander or quickpic to access my photos in onedrive, sometimes it is very slow, or fails to connect. When it does connect, the thumbnails are very slow to load. In the older roms this didn't happen. For me this is a minor issue, because I have other means to access onedrive from my computer. So overall this is a great improvement over the older rom. Thanks to all for your hard work and dedication to improve this device!
I am currently running @greatbal rom on my 5.0 it's equal to this rom, I have to remove supersu manually, I hate when a rom includes root, other than that @greatbal rom runs well on my 5.0.
By the way, did you use windows or linux to install the rom?
vampirefo said:
I am currently running @greatbal rom on my 5.0 it's equal to this rom, I have to remove supersu manually, I hate when a rom includes root. other than that @greatbal rom runs well on my 5.0.
By the way, did you use windows or linux to install the rom?
Click to expand...
Click to collapse
I used windows 7. my only experience with linux, besides Android is through bootable usb drives and cds. I have tried Ubuntu this way. The other bootable drives were mostly window repair, backup, and repartitioning disks.
One note to windows users, there are MANY, UAC promts to to approve the running of the fastboot.exe. So you have to stay with the install to approve each of the many prompts. one workaround would be to go into windows settings and temporarily disable UAC. Then, of course, re-enable it later, after the install finishes. There may be a better way to do this though. Under my fastboot.exe properties, on the compatibility tab, I had it set to always run as an administrator. Maybe that is what caused the constant prompts, not sure. And since I have the device re-partitioned and the rom installed, I don't want to go back and test that theory, since I have installed and updated many apps. It was very nice that you had the re-partitioning built into the script for the install. Just as you stated earlier, be patient, the routine takes some time, the device has not locked up.
I probably wouldn't have bought the Ares 8A, if I had had this rom for my old device. It is too late to return the 8A, now. I haven't figured out how to root the new device, without potentially messing it up.
@vampirefo I hate to ask what is probably a stupid-ass question, but I'm still running Batville. Do I need to re-partition before installing this ROM? If so, it has been a long time since I partioned it for Batville so I'm not sure what the original setup was--can you help? Thanks for continuing to work on the device--we all appreciate it.
zerozed99 said:
@vampirefo I hate to ask what is probably a stupid-ass question, but I'm still running Batville. Do I need to re-partition before installing this ROM? If so, it has been a long time since I partioned it for Batville so I'm not sure what the original setup was--can you help? Thanks for continuing to work on the device--we all appreciate it.
Click to expand...
Click to collapse
@vampirefo included a new partition table with the files. In addition, he put the re-partitioning in the fastboot_cmd.bat, so it is automatic.
martyfender said:
@vampirefo included a new partition table with the files. In addition, he put the re-partitioning in the fastboot_cmd.bat, so it is automatic.
Click to expand...
Click to collapse
Is there any benefit (e.g. speed or battery life) with this rom over batville? I'm assuming that the new one is larger.
zerozed99 said:
Is there any benefit (e.g. speed or battery life) with this rom over batville? I'm assuming that the new one is larger.
Click to expand...
Click to collapse
See my info a few posts above. The issue I am having is with wifi, which I never had in any of the other roms.
I tested with a wifi testing app, and the link speed is good, however, the latency is fluctuating from the norm of 2 ms., all the way up to above 1000 ms. I'm not sure what would cause that, as my tablet is within inches of my wireless router. If anybody has any ideas, please let me know. Web browsing seems ok with Firefox and Chrome, but in apps where I access my photos stored on OneDrive, I have problems. I haven't tried any other internet apps to see if there are any issues. I can access videos with vlc, through my LAN, to my desktop computer with no problems.
zerozed99 said:
Is there any benefit (e.g. speed or battery life) with this rom over batville? I'm assuming that the new one is larger.
Click to expand...
Click to collapse
From my personal experience, the biggest benefit is sound, I can listen to music on tablet without Bluetooth or headset.
The sound through the speaker is loud enough to enjoy.
As time permits, I plan on pulling the sound off of this and if possible apply it to my other roms, that lack good sound through speaker.
If all goes well, just applying sound patch to batville will be all that's needed for batville user's to get same sound quality, without the need to switch to this rom.
Batville is a great rom, just lacks good sound quality through speaker, I hope in time to be able to fix that, with a patch.
Sent from my Life_Max using Tapatalk
@vampirefo, This rom has been the best yet for my 5.0 Ares 8. The only problem I have had is with wifi connectivity. So I decided to start over. I re-ran the fastboot_cmd.bat again to reflash the rom. During the install phase it failed and bricked my device, my first. What did I do wrong to cause this?
I can boot into dnx mode and type fastboot devices, and it lists my Baytrail device. Fastboot flash commands fail with errors. adb commands don't work in this mode.
If I type: fastboot boot boot.img, it boots to uefi / bios access menu. I suspect I need a hub, a usb otg adapter, a keyboard and mouse to get the buttons to respond, though. Are there settings in this bio menu which will help me? Is there any way to recover from this that you know of?
In addition I can boot to an efi shell by holding down the home button and the power button. Unfortunately, your info on the wifi came after I did this blunder. I have a twrp backup, I can't get into it to reload the backup.
Any help recovering from this disaster will be greatly appreciated.
Thanks
Edit: I found this post:
https://forum.xda-developers.com/member.php?u=4821597
Not sure where to get this file: efilinux.efi. Is it the one in your esp folder or the one in the esp.zip?
Thanks
I solved this my self by following @social-design-concepts directions, then running the fastboot_cmd.bat to re-flash the system. Anybody have any ideas what may have caused this data corruption in the first place?
You want me to guess what you did wrong? No ideal, seeing it worked the first time and third time for you, and everytime for me, I would guess user error.
Sent from my Life Max using Tapatalk
vampirefo said:
You want me to guess what you did wrong? No ideal, seeing it worked the first time and third time for you, and everytime for me, I would guess user error.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
No, sorry, this is all I did:
I rebooted to bootloader. Then I ran your fastboot_cmd.bat. It never had errors in the command window until it was running the flash commands. Then it rebooted to the dnx window. So it didn't appear to be a user error. I am using minimal adb and fastboot. I have all of the files in that folder. I shift, right click, then choose open a command prompt here.
Instead of typing the command in windows, I dragged and dropped it in the command prompt window. I guess it will be a mystery. However, I did do a TWRP backup this time, even before flashing SuperSu and busybox.
I did use your fix for the captive portal and my internet seems to have improved, So thanks again.
Just curious, what is the: -S 200M, in the flashing system command?
martyfender said:
No, sorry, this is all I did:
I rebooted to bootloader. Then I ran your fastboot_cmd.bat. It never had errors in the command window until it was running the flash commands. Then it rebooted to the dnx window. So it didn't appear to be a user error. I am using minimal adb and fastboot. I have all of the files in that folder. I shift, right click, then choose open a command prompt here.
Instead of typing the command in windows, I dragged and dropped it in the command prompt window. I guess it will be a mystery. However, I did do a TWRP backup this time, even before flashing SuperSu and busybox. I did use your fix for the captive portal and my internet seems to have improved, So thanks again.
Click to expand...
Click to collapse
I don't use minimal adb, that is a problem, you need to be system-wide.
Use system-wide method, it's a better way to use adb and fastboot. The script was designed to be ran based on system-wide access.
https://forum.xda-developers.com/showthread.php?p=48915118
-S 200M is sparse, the 200M is the size or chunk I tell it to split, this can be raised or lowered depending on speed of computer, I am using a Windows tablet to run the windows batch file.
My Linux could push it much faster, 500 or more, but 200 is safe, slow, and steady.
Sent from my NXA8QC116 using Tapatalk
vampirefo said:
I don't use minimal adb, that is a problem, you need to be system-wide.
Use system-wide method, it's a better way to use adb and fastboot. The script was designed to be ran based on system-wide access.
https://forum.xda-developers.com/showthread.php?p=48915118
-S 200M is sparse, the 200M is the size or chunk I tell it to split, this can be raised or lowered depending on speed of computer, I am using a Windows tablet to run the windows batch file.
My Linux could push it much faster, 500 or more, but 200 is safe, slow, and steady.
Sent from my NXA8QC116 using Tapatalk
Click to expand...
Click to collapse
I had it set at one time in the system environmental variables, but when I redid my system I forgot to re-add it. Thanks for the link. I had seen that in the past, but it had older versions of adb and fastboot. I see now that it has been updated, so thank again.
Edit: I checked and apparently I did have Minimal ADB and Fastboot entered in the system environmental variables, which would make it system wide. I downloaded and installed your recommendation. it added an additional variable after: C:\adb.
Here may be the issue: I updated Minimal ADB and Fastboot with an installer and it appears it added an additional entry for it. I notice to that windows live has two entries also:
C:\Program Files\Mozilla Firefox;C:\Windows\System32;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Minimal ADB and Fastboot;C:\Program Files (x86)\Windows Live\Shared; C:\Program Files (x86)\Minimal ADB and Fastboot;C:\adb.
I think I should remove the double entries?
Here is a link for a microsoft script the remove duplicate path variables:
https://gallery.technet.microsoft.com/scriptcenter/How-to-check-for-duplicate-5d9dd711
I ran that script, but my entries remain the same. i'm not sure why.
I guess the simplest solution is to remove Minimal ADB and Fastboot, its variables and keep the other ADB.
This Ares 8 which originally came with 5.0 is running great since I redid it and applied your wifi fixes to it.
I find myself using it most of the time, over the new Ares 8A, because I have root on it and don't possess enough knowledge to feel safe in trying to root the Ares 8A, or building a working TWRP for it.
By the way, I had 98% battery left after leaving it overnight. That is a far cry from what I had with the 701Q and Batville roms. That is great.
With Batville I could never get contacts to work, despite trying playstore and other fixes. In addition, the sound is good with this new rom.
I don't do much gaming anymore, but i do have GT Racing 2 installed on the External microSD card, Using @vickybonick Apps2SD, and this graphic intensive game runs very well on it.
Thanks again for your great work.
By the way, in the past with the original 5.0 rom, I tried using three different SanDisk high speed UHS-1, Class 10 cards with Apps2SD, and all of them had good write speeds, but poor read speeds. I finally returned those cards and went with the Samsung EVO series. The read and write speeds are great on this card. I used several test apps, both on Windows and Android, to test them. Has anybody else had similar experiences with different brands of high speed cards?
If you have more than one adb install listed in the environmental variables, the first listed takes precedence in system wide access. I tested this by changing the order with Rapid Environment Editor. I viewed which one was running in Process Explorer.
Rapid Environment Editor will also show any invalid paths. This is of academic interest, as the simplest solution, is of course, to only have one adb installed system wide. If you run a command prompt from the folder where each adb is installed, that one will run, instead of the one installed system wide, unless you are already in the folder where the system wide is installed. (shift right click, choose open command prompt here).
That is what I did and should have worked fine, it always has before. So I am "beating a dead horse to death", in the pursuit of knowledge. i hope this helps someone else as well, that is learning, like me. By the way, is this considered OT?
I hate to be a thorn in your side, but:
Apparently I spoke too soon about the wifi connection working better. And please keep in mind I am comparing it to what I had on all three previous roms: the original 5.0, i708q and the Batville roms, and my newer Ares 8A. Also please keep in mind that the device is less than 2ft. from my wireless router in my tests.Using WiFi Network Analyzer, I see a continual fluctuation in the dBm signal strength, all the way from the normal -34, all the way up to the -70 to -92 range. In addition, the latency goes from normal 3-4 ms., all the way into the hundreds and even thousands ms. The older roms did not do this in the analyzer. My new Ares 8A remains in the -32-42 dBm signal strenth, and the latency stays in the 3-4ms range.
I seem to have improved things slightly by changing the following things in my router:
Allow n devices only
bandwidth set from auto 40mhz/20mhz, to 20mhz only
protected mode (not to be confused with WPS):
rotected Mode
NOTE: In most situations, best performance (throughput) is achieved with Protected Mode OFF. If you are operating in an environment with HEAVY 802.11b traffic or interference, best performance may be achieved with Protected Mode ON.
(I'm not certain if protected mode helped, or not.)
Is there anything I can do on the tablet to improve this or troublshoot it?
Furthermore are the system wifi files in the newer rom different to what was in the working i708q and Batville roms? Sometimes, turning off wifi and turning it back on helps for a while. Also I forgot to point out that the fan shaped wifi connection symbol fluctuates from full to partial, also. All other devices I have turned on to test, show no problems, that I can tell.
I haven't ruled out interference as I live in an apartment complex where I can see several neighbors on all non-overlapping channels 1, 6 and 11. However the older roms, the new 8A and other tested devices have no detectable problems with my wireless router. Does anybody have any suggestions?
Like I've said in the past this is a great rom for this device, if I can get this problem resolved.
Thanks
For my wireless configuation and router, I was able to improve my speed and connection by reading linux documentation on the hostapd.
I edited the hostapd.conf located in system/etc/wifi, changing the following entries:
preamble=0
dissoc_low_ack=0
I'm not sure, but maybe my wireless router doesn't handle the default settings as well?
If that was the case, though, why did the same defaults work well with the previous roms?
preamble=0 "Set optional use of short preamble."
0 sets a long preamble instead of a short one
dissoc_low=0 "Disassociate stations based on excessive transmission failures or other indications of connection loss. This depends on the driver capabilities and may not be available with all drivers."
0 turns this off.
My congested wireless environment may be partially to blame for this. there are at least 4 clients on each of the three non-overlapping channels of 1,6 and 11, respectively.
If anybody has any additional thoughts on this, let us all know.
Thanks
UPDATE: apparently, the above changes didn't help. In the terminal when I type: busybox ifconfig, I see dropped packets under p2p and wlan0 for rx, but not for tx. This has happened on other wireless networks as well. Maybe not as bad though. I'm not 100% sure though as I haven't run ifconfig on those other networks.
I am considering ordering an ASUS 3-In-1 Wireless Router (RT-N12), or an Asus RT-N12 D1 Wireless Router - IEEE 802.11n RT-N12/D1, to see if this improves things. I have no AC devices, so an AC router seems like a pricey overkill for me. However an AC might be more future proof. I don't have a new flat screen tv to stream to. I have an old Sony 36" CRT, which I haven't turned on for over a year, as I watch streamed TV shows on the internet, from my computer. So finally, the bandwidth that AC affords, doesn't seem necessary.
Well, I managed to (sort of) kill my Ares 8. I already had 5.1 installed and working an thought, "I'll run this and start fresh." Everything looked like it went normally but when the tablet rebooted, I have:
Entering DnX mode.
Waiting for fastboot command...
Tethered recovery gets this:
***********************************************************************
FASTBOOT TETHERED RECOVERY LAUNCHER 07-24-2015
***********************************************************************
=======================================================================
DEVICE STATUS: FASTBOOT-ONLINE
DEVICE INFORMATION: BaytrailBA302518 fastboot
=======================================================================
copy needed files to our device
sending '/tmp/recovery.zip' (7151 KB)...
OKAY [ 0.285s]
writing '/tmp/recovery.zip'...
FAILED (remote: unknown command)
finished. total time: 0.294s
sending '/tmp/recovery.launcher' (704 KB)...
OKAY [ 0.036s]
writing '/tmp/recovery.launcher'...
FAILED (remote: unknown command)
finished. total time: 0.049s
we need to stop logcat before replacing it
...
FAILED (remote: unknown command)
finished. total time: 0.005s
sending '/system/bin/logcat' (349 KB)...
OKAY [ 0.021s]
writing '/system/bin/logcat'...
FAILED (remote: unknown command)
finished. total time: 0.026s
issue fastboot oem "stop_partitioning" command to start cwm recovery:
...
FAILED (remote: unknown command)
finished. total time: 0.005s
Everything tethered or not comes up (remote: unknown command)
martyfender what exactly did you do to get tethered recovery to work?
N810E said:
Well, I managed to (sort of) kill my Ares 8. I already had 5.1 installed and working an thought, "I'll run this and start fresh." Everything looked like it went normally but when the tablet rebooted, I have:
Entering DnX mode.
Waiting for fastboot command...
Tethered recovery gets this:
***********************************************************************
FASTBOOT TETHERED RECOVERY LAUNCHER 07-24-2015
***********************************************************************
=======================================================================
DEVICE STATUS: FASTBOOT-ONLINE
DEVICE INFORMATION: BaytrailBA302518 fastboot
=======================================================================
copy needed files to our device
sending '/tmp/recovery.zip' (7151 KB)...
OKAY [ 0.285s]
writing '/tmp/recovery.zip'...
FAILED (remote: unknown command)
finished. total time: 0.294s
sending '/tmp/recovery.launcher' (704 KB)...
OKAY [ 0.036s]
writing '/tmp/recovery.launcher'...
FAILED (remote: unknown command)
finished. total time: 0.049s
we need to stop logcat before replacing it
...
FAILED (remote: unknown command)
finished. total time: 0.005s
sending '/system/bin/logcat' (349 KB)...
OKAY [ 0.021s]
writing '/system/bin/logcat'...
FAILED (remote: unknown command)
finished. total time: 0.026s
issue fastboot oem "stop_partitioning" command to start cwm recovery:
...
FAILED (remote: unknown command)
finished. total time: 0.005s
Everything tethered or not comes up (remote: unknown command)
martyfender what exactly did you do to get tethered recovery to work?
Click to expand...
Click to collapse
I didn't use a tethered recovery, I used the twrp recovery posted at the start of this thread. It is in the ares8_5.0_upgrade_5.1.zip.
When I had similar problems, I found a post by [MENTION=5368024 [user=4821597]@social-design-concepts[/user] https://forum.xda-developers.com/showpost.php?p=65435780&postcount=409 in the original ares 8 thread to fix the problem:
"
Member
94 posts
Thanks: 30
Quote:
Originally Posted by social-design-concepts
"thats the uefi / bios access menu you'll need an usb otg adapter and most devices ( not all ) require use of a powered usb hub ( which i personally recommend regardless as devices that use more power can short out the port ) and keyboard and mouse to navigate it. but it looks as if you esp is corrupt if you have the efiloader and droidboot.img you can try.
Code:
fastboot flash osloader efilinux.efi
fastboot boot droidboot.img
this should get you back into droidboot / fastboot where you can then partition your device and reflash the esp and the reset of android.
@social-design-concepts, thanks for this post. When I tried to reinstall vampirefo's latest 5.1.1 rom, ported to work on the 5.0 device, it failed and Could only get into dnx mode. I used your instruction to fix the ESP partition, then reinstalled the rom, with no problems. It is running great now.
Thanks, again."
I used the above commands and files within the rom posted above, so I didn't even need a usb otg adapter to do it. I believe I used the droidboot.img and efilinux.efi. The efilinux.efi is in the esp.zip. unzip to the root of your folder where you have adb and fastboot installed. The rom files must also be unzipped to that location.
The above commands are run through an adb and fastboot command prompt, from your computer. Those are the windows commands. they would be slightly different if you are on linux. Then I rebooted the tablet back into fastboot mode: fastboot reboot bootloader, which worked again, ran the fastboot_cmd.bat to reflash the rom again. This was all done from the computer with an adb and command prompt, using fastboot commands, of course. Type fastboot devices, to make sure your device is showing up, before proceeding
I never figured out the cause of the problem when I reflashed this rom the second time, but I suspect I should have done a factory reset before doing it. It was flashing the above files that gave me the ability to get into fastboot bootloader again, then I reflashed the whole rom the third time and it worked as it did the first time I did it.
Currently I am using the newer, twrp 3.1 recovery he posted in the ares 8 5.1 problems thread.
UPDATE: if you don't have a permanent recovery installed, this may or may not work in the tethered, temp, twrp recovery. I don't know as I have never used the tethered, temp, recovery.
Actually, I think I used the fastboot commands in dnx mode to flash the droidboot.img and efilinux.efi, rebooted into the bootloader: fastboot reboot bootloader and then ran the fastboot_cmd.bat to reflash the rom.
And of course, you have to make sure adb and fastboot drivers are setup correctly and recognizing your device, for all of the above to work. I tried to retrace my steps. I hope I didn't forget any of them!
Good Luck!
For background, I have Verizon pixel 2 and am using a Mac.
I went down a massive rabbit hole last night reading through these forums and all the posts and was able to unlock bootloader, flash the January OTA and then root by doing the modified boot file with magisk. (interestingly enough the booting into recovery gives me red ! Over a dead Android and I could not load the OTA that way, nor did the adb sideload OTA comand work either, I had to push the extracted walleye img and then the zip file as discussed in one of the steps in some other thread here)
So anywho, in the end I now have a phone that gives me 2 errors when it reboots, one for unlocked bootloader and another for root telling me something is wrong with my phone and i should contact the manufacturer (which I read on here is normal), but my biggest issue is that my ADT alarm app doesn't work anymore (even if i check it off for hide in magisk). I feel like the root is just not worth it for me and I want to revert to completely stock image, even if it resets my phone and I have to re back everything up all over again like did when i had to do the unlocking of the boot loader.
So -- What are the steps I should take?
1)uninstall magisk from magisk manager?
2)delete magisk manager?
The above will unroot me, correct?
3)Do I push the stock boot image file onto the phone?
4) do I have to repush the latest OTA walleye image and zip file onto the phone again?
5) do I then do the adb reboot and do the flashing lock command (same command i did to unlock the boot loader) to lock up the bootloader and reset to stock?
If someone could be as explicit as possible in correctiong or validating my steps above it would be much, much appreciated.
I don't want to do any more unnecessary steps in flashing things than is needed so if I have extra steps above (perhaps 4 is not needed?) Let me know.
Thanks
Proceed with Caution
I am not an expert by any means, but can speak from personal experience. I was in the exact same situation as you. I followed the detailed steps to unlock the bootloader on my pixel 2, received similar issues, and the same prompt when the phone rebooted. All that to say proceed with caution.
My thoughts on questions 1 & 2: I personally wouldn't recommend you remove or delete magisk from the manager. When I did i had to reinstall it via twrp. My phone functioned fine, apart from the error at reboot.
My thoughts on questions 3 -5: When I followed the steps on XDA for your questions here I ended up bricking my Pixel 2 with locked bootloader from Verizon. Probably an error on my part, but wouldn't want someone else to go through the headache, hours of issues, and then an expensive paper weight.
My suggestion would be to:
1. Leave your phone as is and attempt to trouble shoot the app or apps you are having issue with
2. contact Google support on your phone and see if they would replace it
3. wait for an established method to unroot the pixel 2 here
Thankfully Google replaced my phone due to the error after rebooting, prior to me bricking it. I knew I had a replacement phone coming. So I attempted to go back to stock and that is when I messed it up.
Note sure this is exactly what you were looking for, but hope this helps you.
Dozens of posts with hundreds of pages on how to root but no advice on how to go back to stock cleanly?
iridium7777 said:
Dozens of posts with hundreds of pages on how to root but no advice on how to go back to stock cleanly?
Click to expand...
Click to collapse
Your version is Verizon which is making things more complicated. Generally when the bootloader is unlocked, you just hit flash-all.bat and then relock the phone. Given that the Verizon I'm not sure.
So you are on stock ROM with all these apks loaded ? If you go to settings, then do a factory data reset, you'll reset the phone back to stock and completely wipe the phone and return it to stock, at that point you can go into bootloader mode and relock.
Again your bootloader is unlocked, so the flash-all is your best option. If you see the red exclamation point with the error android laying on his back, you press power and up volume and toggle that and it will bring in the stock recovery which you can sideload the OTA however it may fail since you have magisk.
I bought my phone stock last year and have not rooted it or modified it in anyway. Too many problems and it only gets harder and harder as Google releases a new phone.
@mikeprius -- thank you for replying. after reading more on here, it seems like that's the way to go -- flash-all script, seems like i don't really need to do 1&2 that i wrote above as the flash-all will wipe that out by itself.
at that point i should be running the latest stock 8.1 but with an unlocked bootloader (and according boot up message screen) and i should be able to re-do the fastbook unlocking command to lock the phone back up.
(and yes, after reading even more now -- and i tried this yesterday -- i completely missed the portion about PWR + Vol Up button, that's why i think i had that issue, but still, i was able to push the update by pushing img and then the zip through).
iridium7777 said:
@mikeprius -- thank you for replying. after reading more on here, it seems like that's the way to go -- flash-all script, seems like i don't really need to do 1&2 that i wrote above as the flash-all will wipe that out by itself.
at that point i should be running the latest stock 8.1 but with an unlocked bootloader (and according boot up message screen) and i should be able to re-do the fastbook unlocking command to lock the phone back up.
(and yes, after reading even more now -- and i tried this yesterday -- i completely missed the portion about PWR + Vol Up button, that's why i think i had that issue, but still, i was able to push the update by pushing img and then the zip through).
Click to expand...
Click to collapse
If I were in your situation and the bootloader is unlocked, just use flash-all which has a wipe script then call it a day. I think trying to screw around even more is just a waste of time and I wouldn't even bother with the OTA, just erase and flash stock. You don't have to relock your bootloader if you don't want to, if you stay fully stock you may still be able to get OTA updates. I'm not sure if a bootloader locked is required someone can chime in as it has been awhile since I've done this, but over 1 yr ago, I just kept the bootloader unlocked, kept things stock and everything was good to go. Obviously there are security issues with an unlocked bootloader, but I'm sure you know this already
@mikeprius you keep saying reset/erase, do you suggest i re-set the phone and then flash the stock image?
i was just going to flash the stock image, i figured it already wipes the phone, and locking the bootloader would wipe it again, so what's the point of erasing all data prior?
Not to hijack this thread, but a question to add... I thought that there were kernels that would mask certain things to allow all of those apps to work, and get rid of the "problem with device" message.
Is that correct?
iridium7777 said:
@mikeprius you keep saying reset/erase, do you suggest i re-set the phone and then flash the stock image?
i was just going to flash the stock image, i figured it already wipes the phone, and locking the bootloader would wipe it again, so what's the point of erasing all data prior?
Click to expand...
Click to collapse
Just flash the stock images. It will auto reset.
Again, don't mess with anything just flash stock images, then go from there.
Also flash the newest version of the stock images out there. The pixel 2 will error if you try to downgrade any version.
here are all the steps to UNROOT and LOCK the boot loader on your Pixel 2 on a Mac (windblows users simply ignore all the "./" references).
1) download the latest ADB tools from google
2) download the latest factory Walleye image
3) unzip files from 1&2 into a common directory
4) edit flash-all.sh file and add "./" infront of every instance of "fastboot" in the script [windows users ignore this step]
5)hook up your phone to your computer in debug and file transfer mode. check that "./adb devices" loads your devide
6)type " ./adb reboot bootloader"
7) check that your device is still connected by typing "./fastboot devices"
8) type "./flash-all.sh"
===the script will run and your phone will be restored to stock, and UNROOTED. upon boot up skip through all of the setup steps and get to the phone settings as fast as you can. enable developer option, enable debug mode, set phone to data transfer ====
9) check that your phone is connect to your computer by "./adb devices"
10) type "./adb reboot bootloader"
11) check your devices is still connected by "./fastboot devices"
12) type "./fastboot flashing lock"
===== this will re-wipe your device again, you'll see the circle of death, and this will LOCK your boot loader back up again======
side note, feel free to skip over the steps where you check that your phone is still connected to the computer (./fastboot devices) if you're less paranoid and comfortable.
iridium7777 said:
here are all the steps to UNROOT and LOCK the boot loader on your Pixel 2 on a Mac (windblows users simply ignore all the "./" references).
1) download the latest ADB tools from google
2) download the latest factory Walleye image
3) unzip files from 1&2 into a common directory
4) edit flash-all.sh file and add "./" infront of every instance of "fastboot" in the script [windows users ignore this step]
5)hook up your phone to your computer in debug and file transfer mode. check that "./adb devices" loads your devide
6)type " ./adb reboot bootloader"
7) check that your device is still connected by typing "./fastboot devices"
8) type "./flash-all.sh"
===the script will run and your phone will be restored to stock, and UNROOTED. upon boot up skip through all of the setup steps and get to the phone settings as fast as you can. enable developer option, enable debug mode, set phone to data transfer ====
9) check that your phone is connect to your computer by "./adb devices"
10) type "./adb reboot bootloader"
11) check your devices is still connected by "./fastboot devices"
12) type "./fastboot flashing lock"
===== this will re-wipe your device again, you'll see the circle of death, and this will LOCK your boot loader back up again======
side note, feel free to skip over the steps where you check that your phone is still connected to the computer (./fastboot devices) if you're less paranoid and comfortable.
Click to expand...
Click to collapse
hey there. what is the command suppose to look like? every combination I try gives me an error:
first, I don't even enter the Fastboot command the same wayit given me an error:
Asads-MacBook:~ asad$ ./fastboot devices
-bash: ./fastboot: No such file or directory
so I try this: Asads-MacBook:~ asad$ fastboot devices
[serial #] fastboot
these are all the errors I get:
Asads-MacBook:~ asad$ cd /Users/asad/Desktop/walleye-opm1.171019.021
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: fastboot./: No such file or directory
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: ./fastboot: No such file or directory
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
fastboot: usage: unknown command ./flash
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: fastboot./: No such file or directory
...
how is the command suppose to look that I can edit it the right way?
"fastboot: No such file or directory" means that you didn't do step 1, step 3 on the file you didn't download, and there should probably be a "cd /<whatever the 'common directory'>" is. (I just created a directory named adb. That's good enough for me to know what it's for.)
You have to download adb and fastboot (which come in the adb tools file), unzip them to whatever directory you're going to use for flashing the phone, and cd to that directory.
Then, since you're evidently on MacOS, each command has to have ./ in front of it (that says "the current directory"). Try all that, then see what happens.
Rukbat said:
"fastboot: No such file or directory" means that you didn't do step 1, step 3 on the file you didn't download, and there should probably be a "cd /<whatever the 'common directory'>" is. (I just created a directory named adb. That's good enough for me to know what it's for.)
You have to download adb and fastboot (which come in the adb tools file), unzip them to whatever directory you're going to use for flashing the phone, and cd to that directory.
Then, since you're evidently on MacOS, each command has to have ./ in front of it (that says "the current directory"). Try all that, then see what happens.
Click to expand...
Click to collapse
yayy! that worked!
so i had adb and fastboot in a folder (platform-tools) and i had the factory image in its own seperate folder (walleye-files). i was making the cd; walleye folder and trying to flash-all.sh there.
so i had to put the files from the walleye folder into the platform-tools folder. Then I made platform-tools the cd. now when . i could now follow all the steps from 4-12 and got the pixel 2 the way it was OTB.
thanks!
Great! I'm not a Mac expert (last time I used one was the 128K Mac in 1985), so I'm not sure how to export a path in MacOs, so I gave you the complicated way, but you got it done anyway. (If you ever find out how to add the platform-tools folder to your path, you can leave adb and fastboot in there and keep the ROMs [walleye] in their own folder, cd to it and adb and fastboot will still work.)
QLink Serrano 3
Model No. HPP-L55B
By Hot Pepper Mobile
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bootloader Unlocking
And Rooting Guide
OVERVIEW:
This guide provides step-by-step instructions for unlocking the bootloader and achieving root access on the QLink Serrano 3. Please note that this guide is specifically for the QLink variant of the Serrano 3 (HPP-H55L), as I have not verified the applicability of this guide on other carrier variants of this smartphone. To simplify the rooting procedure, and to cater this guide to new and inexperienced members, I have provided a boot image pre-patched for Magisk systemless root support below, in the downloads section.
IMPORTANT NOTE: The pre-patched boot image in the downloads section below corresponds with firmware build HPP-L55B-J-9.0.0. If your Serrano is running a different build, flashing the pre-patched boot image provided may or may not result in compatibility issues. In short, the best rule of thumb when achieving systemless root is to always patch an image that matches the firmware build installed on your device, otherwise you may encounter issues such as broken WiFi, broken Bluetooth, or your device may not boot at all. Should any members encounter issues of this sort, you may flash your device with the HPP-L55B-J-9.0.0 firmware by following my firmware restoration guide for the Serrano here: QLink Serrano 3 Firmware Restoration Guide
PREREQUISITES:
You will need a Windows PC or laptop with the ADB & fastboot tools installed. I have provided a link below for the latest Minimal ADB & Fastboot tools. You will need the factory supplied, or a quality equivalent micro USB to USB-A data syncing/charging cable. And, you will need your QLink Serrano 3 smartphone. I again emphasize that this guide has only been tested on the QLink variant of the Serrano (HPP-L55B).
DISCLAIMER:
The tasks outlined in this guide encompass inherent risks to the integrity and operability of your smartphone. Moreover, unlocking the bootloader/rooting the device will void any active manufacturer's warranty you may have on your Serrano. By proceeding further, you are assuming full responsibility for the state and health of your smartphone. As such, you are hereby absolving me of any responsibility or civil liability in the unfortunate event things go badly. This guide has been fully and thoroughly tested. Follow the instructions carefully, employ some patience, and pay attention to detail and I'm confident things will go smoothly. It should also be noted that the tasks outlined herein can be carried out using a Mac or Linux computer as well. This particular guide, however, will focus solely on a Windows -based setup.
I.. INSTALLING ADB & FASTBOOT
Because both tasks outlined in this guide require ADB/Fastboot communication between your phone and PC/laptop, this first section will focus on proper installation of the ADB & Fastboot utilities on your Windows computer. If you already have a working ADB/Fastboot environment, skip down to the next section on unlocking the bootloader. Otherwise, follow these steps:
Download the Minimal ADB & Fastboot tools installer from the link below. Right click the .exe file and opt to run it as an administrator. Follow the on-screen prompts and complete the installation;
Open the Windows File Explorer, go to This PC and open your C: drive directory. Open Program Files x86 and locate the Minimal ADB & Fastboot folder. Copy the folder and then paste it on your desktop (this step merely configures the ADB & Fastboot directory to a more convenient location from which to work);
Open the Minimal ADB & Fastboot folder and double click the file named cmd-here. A command prompt will open. Next, connect your Serrano to your Windows computer using a suitable micro USB to USB-A data syncing cable. Ensure that USB Debugging is enabled in your Developer Options menu.
In the command window you opened in the previous step, execute this command:
Code:
adb devices
Watch your device display for a USB Debugging authorization prompt. Grant the request. If properly connected, the command window will output an alphanumeric string consistent with your device serial number;
If the command window does not display your serial number, or if you get a WAITING notification, your smartphone isn't communicating properly with your PC or laptop. Try another data syncing cable,; change USB ports; and/or reinstall the Minimal ADB & Fastboot tools on your computer;
Once you have established proper device communication, we will now test fastboot mode communication. Execute this command:
Code:
adb reboot bootloader
Your device should now boot into fastboot mode, which will be illustrated by a darkly backlit display with the words => FASTBOOT mode.... displayed in a white font at the bottom-left of the screen;
Next, execute this command:
Code:
fastboot devices
Similar to before, if properly connected, the command window will display your device S/N. If you don't see your S/N, or if the command window says WAITING, you are not properly connected. Again, try changing USB ports, try another data syncing cable, and/or reinstall the Minimal ADb & Fastboot tools on your computer.
II. UNLOCKING THE BOOTLOADER
WARNING: Unlocking the bootloader triggers a native Android security mechanism that forces the device into a factory data reset. This will erase all saved userdata on your phone. Before proceeding further, make a backup of all saved userdata you wish to keep.
Open device Settings>System>Developer Options, and enable the OEM Unlock option;
Boot into fastboot mode by executing:
Code:
adb reboot bootloader
Once in fastboot mode, it's time to initiate bootloader unlocking. Execute this command:
Code:
fastboot flashing unlock
Your smartphone display will now prompt you to tap Volume + to proceed with unlocking, or Volume - to cancel;
After pressing Volume +, the unlock sequence will finish in just a few seconds. Now reboot to complete the process: Execute:
Code:
fastboot reboot
As mentioned previously, your phone will now initiate a mandatory factory data reset, after which your device will boot into the initial setup phase of the Android OS. Your bootloader is now officially unlocked.
III. ROOTING THE SMARTPHONE
Now that the bootloader is unlocked, attaining root access is very straightforward.
Download the patched boot image and vbmeta image files from the links below and save the files in your Minimal ADB & Fastboot folder;
Double click the cmd-here.exe file to open a command window. Execute this command to flash the patched boot image:
Code:
fastboot flash boot patched_boot.img
Now we will disable dm-verity by executing this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Now, execute this command to reboot your phone:
Code:
fastboot reboot
Upon reboot into the Android OS, locate the Magisk app or its stub placeholder in your app drawer. Open Magisk, grant any requested permissions, and follow any prompts to finish setting up the root environment. Magisk may initiate a reboot to complete root setup. If the Magisk app or its stub placeholder is not in your app drawer, download the Magisk v25.2 APK from the link below and install it on your phone. That's it. You are rooted with the Magisk v25.2 systemless root solution.
DOWNLOADS:
• Minimal ADB & Fastboot v1.4.3
• Patched boot.img
• vbmeta.img
• Official Magisk Releases (GitHub)
Thank you for this I'm going to try this. Here are some of the issues I have been having. When I plug it in to charge it. It keeps trying to boot and will not stop. I have to press the power button to buy bypass an error message that says this device is corrupted. I just got this phone from qulink (Amazon) and it was doing this since I opened it. It will not update the system. I believe the boot issue may have something to do with it. I'm not sure what kind of bloat wear it has but I do know something is running rapidly in the back ground I have practically no battery life and charging it is a night near. Another important question is can I use a chrome book to do the procedure? Any input would be greatly appreciated.
Thanks
John Bridges
John Bridges said:
Thank you for this I'm going to try this. Here are some of the issues I have been having. When I plug it in to charge it. It keeps trying to boot and will not stop. I have to press the power button to buy bypass an error message that says this device is corrupted. I just got this phone from qulink (Amazon) and it was doing this since I opened it. It will not update the system. I believe the boot issue may have something to do with it. I'm not sure what kind of bloat wear it has but I do know something is running rapidly in the back ground I have practically no battery life and charging it is a night near. Another important question is can I use a chrome book to do the procedure? Any input would be greatly appreciated.
Thanks
John Bridges
Click to expand...
Click to collapse
Greetings @John Bridges. You have come to the right place. Sounds like you're stuck in a classic boot loop. Flashing the factory firmware offered in my guide should certainly restore your device to its stock factory state.
The firmware, unfortunately, does include the typical bloatware specific to QLink devices. Of course,, once you get your phone restored via firmware flashing, you can always opt to unlock your bootloader, achieve root and debloat tie stock OS. So, your best option may be to first restore your device by installing firmware, and then rooting.
Serrano Firmware Restoration Guide
Greetings Viva,
Thanks for the great response. I will try your great advice and respect you for dedicating you're time to help the Android epidemic.
John Bridges said:
Greetings Viva,
Thanks for the great response. I will try your great advice and respect you for dedicating you're time to help the Android epidemic.
Click to expand...
Click to collapse
Thank you for the kind words. The type of boot loop you are experiencing is caused from data corruption that occurs when Android decrypts the /userdata partition during the boot sequence. By default, Android encrypts all data on this partition for user security; as such, whenever your device boots up, Android decrypts the data to make it accessible. If any errors or data corruption are incurred during this process, you will be promoted to either try again or perform a factory data reset.
Sorry I just saw your reference to the Chromebook. I'm afraid it won't be much help on this. My guide focuses on a Windows setup; however, Linux or Max can also be used. Out of curiosity, have you first tried factory resetting the phone?
Yes I did still didn't help When I'd tried to start it a message would appear saying the device is court press power button to continue and it came out of the box with this problem. I tried to update it and several different errors would show up,one was something about OTA, Would it be possible to do the procedure with a chrome book?
John Bridges said:
Yes I did still didn't help When I'd tried to start it a message would appear saying the device is court press power button to continue and it came out of the box with this problem. I tried to update it and several different errors would show up,one was something about OTA, Would it be possible to do the procedure with a chrome book?
Click to expand...
Click to collapse
The device is court I mean.
Corrupt I mean
John Bridges said:
Corrupt I mean
Click to expand...
Click to collapse
I understand on the device being data corrupted. Firmware restoration is definitely your best option. I know of no way to flash firmware using a Chromebook. I'll research it and see if it can be done.
Okay I did find an XDA guide on utilizing ADB & fastboot on Chromebook. https://forum.xda-developers.com/t/...-chromeos-adb-fastboot.2157230/#post-38232908
However, even the developers who posted in that thread refer to the procedure as extremely complex.
@John Bridges have you had any luck with restoring your firmware via Chromebook?
For those members who detest the abundance of bloatware included in the factory firmware package, I have unpacked the super.img, removed a considerable amount of the QLink apps, services and other bloatware, and then repacked the super.img. I have removed the annoying QLink lock screen, the QLink "free WiFi" service, a number of the preinstalled Google apps, and some other RAM demanding apps & services. I've noticed a remarkable improvement in performance on my own device as a result of debloating the stock OS in this manner.
I will post a new thread this weekend with this debloated stock OS, and instructions for fastboot installation. You will need an unlocked bootloader to install it.
VivaI
I just haven't had time to do it yet I am anxious to do it however and I will let you know how it went for sure.
VivaI and others,
It is a shame that people like myself that have to get these government phones to have one or hacked and it's a great thing you all are doing to give us a phone that will be actually uncorrupted. I don't know if this matters but the phone I got was from Amazon and it is supposed to be unlocked I don't know if that means the bootlegger is unlocked or anything else but I thought it may be helpful to you to know this.
John Bridges said:
VivaI and others,
It is a shame that people like myself that have to get these government phones to have one or hacked and it's a great thing you all are doing to give us a phone that will be actually uncorrupted. I don't know if this matters but the phone I got was from Amazon and it is supposed to be unlocked I don't know if that means the bootlegger is unlocked or anything else but I thought it may be helpful to you to know this.
Click to expand...
Click to collapse
And I'm talking about the phone or the replacement phone you get from q Link it is supposed to be unlocked and it comes from Amazon I checked on it online.
John Bridges said:
And I'm talking about the phone or the replacement phone you get from q Link it is supposed to be unlocked and it comes from Amazon I checked on it online.
Click to expand...
Click to collapse
To the best of my knowledge -- but not confirmed 100% -- all variants of the Serrano are GSM unlocked. Mine originally came from Amazon as well. By unlocked, I am referring to network unlocked and not the bootloader.
Very nice to know! I'm going to try and get it done tomorrow.
John Bridges said:
Very nice to know! I'm going to try and get it done tomorrow.
Click to expand...
Click to collapse
If you have any questions, or if you encounter any obstacles during the procedure, just let me know.
Viva La Android said:
For those members who detest the abundance of bloatware included in the factory firmware package, I have unpacked the super.img, removed a considerable amount of the QLink apps, services and other bloatware, and then repacked the super.img. I have removed the annoying QLink lock screen, the QLink "free WiFi" service, a number of the preinstalled Google apps, and some other RAM demanding apps & services. I've noticed a remarkable improvement in performance on my own device as a result of debloating the stock OS in this manner.
I will post a new thread this weekend with this debloated stock OS, and instructions for fastboot installation. You will need an unlocked bootloader to install it.
Click to expand...
Click to collapse
Could you share the link to this thread please? The search function on this forum is frustrating and not turning up any relevant results and with your profile set to private I coludn't search for your threads either.
Crap nevermind, I just noticed I could pull up threads you created using the search function and looks like it hasnt been posted yet. Could you update this thread when it is?
GIutton said:
Could you share the link to this thread please? The search function on this forum is frustrating and not turning up any relevant results and with your profile set to private I coludn't search for your threads either.
Crap nevermind, I just noticed I could pull up threads you created using the search function and looks like it hasnt been posted yet. Could you update this thread when it is?
Click to expand...
Click to collapse
Not finalized. There are bugs to work out.
Anyone know why we can't modify, add, or remove files from the system partition using an app like root explorer? I wanted to change my bootanimation on my hot pepper serrano 3 and remove unwanted apps and files since i now have it rooted with magisk 25.2 but system partition seems to be read only at the moment. You can delete stuff from the system partition but they come back after a reboot. Same goes with modifying or adding anything in /system. You need to mention in the OP that we only have partial root not full root. Can anyone confirm this and is there a solution to this problem? Is it just me that is having this issue?
I am trying to root my new Pixel 7 Pro, build number TD1A.220804.031, but have run into an issue. Let me explain what I have done and where the issue arose:
I am following the instructions here: https://www.xda-developers.com/how-to-unlock-bootloader-root-magisk-google-pixel-7-pro/. I found the factory image for my phone, downloaded it, then downloaded/installed the Payload Dumper Tool, extracted init_boot.img, copied it to my phone, patched it using Magisk, and copied it back to my computer. Took a bit longer than expected, but no problems.
Via the phone’s setting, I enabled OEM Developer options and then allowed OEM Unlocking. Again, no issues. I then turned the phone off, attached the phone to my computer using a USB cable, and then booted it so that the bootloader menu was visible. In a command window on my PC, I then ran ‘fastboot flashing unlock’. I think this worked (because, when I restarted the phone, I had to go through the whole initialization process again).
The next step is where I ran into the problem. The first time, I put the modified init_boot.img in a new folder on the C: drive, but when I ran ‘fastboot flash init_boot path/to/magisk_patched.img’, I got the error “fastboot: error: cannot load <patched file>: permission denied”. So, then I copied the file to a folder on D:, ran the same command, and got the same error.
I suspect that I missed a step or something equally silly. Any suggestions as to what I should try or any pointers to other rooting guides that might be helpful? Don’t know if this means anything, but when the phone was powered off and plugged into the computer, I tried ‘adb reboot bootloader’ but nothing happened.
When you reboot, do you get the orange triangle with exclamation in it?
it might just be easier to move the magisk_patched.img to the platform-tools folder (the same folder that has adb.exe and fastboot.exe); if you are having "permission" issues from Windows, but you aren't from adb or fastboot, then supposedly having it in the same folder should run it under the same permissions.
Also, make sure that you run CMD as an elevated prompt; search for CMD, right-click, and "Run as administrator" -- this might help with the permission issues as well.
Final suggestion is to be sure to run platform-tools version r33.0.3...
Good luck and hope this helps...
P.S. Also, you might've had better luck and/or it's better organized if you posted in the Pixel 7 Pro (cheetah) forum instead of the Pixel 7 (panther)....
Use Pixel Flasher. Less hassle, more convenience.