Database Info

[Solution]Windows 8 - ADB/fastboot driver problem solved!!

Hello!!​
First off; This is copied, from my thread, in the Galaxy Nexus forum... Sorry, if you find the words "Galaxy" or "Samsung". But, this works for pretty much every phone, (except, for the USB drivers)...
{
"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"
}
So, give it a go...
I haven't found another tutorial, like this at all... So, if you find something like this it's copied from me
Now, on to the actually interesting stuff ^^
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Note: If you feel more comfortable using the Windows Power Shell, you can use that as well, it is, after all, only the Windows shell
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... :
Code:
[B][COLOR="Cyan"]devmgmt.msc[/COLOR][/B]
Now, the device manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here
To prevent confusion: When I say install, it can mean unpack, or install... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed. Again (-_-") ) (Note: These are the Sammy OEM drivers.)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has popped up, choose "Browse my computer" and goto your desktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check out Beatsleigher & M4gkman's Universal Android Toolkit, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your Android Device!!!!
So, apparently, if you're using Windows 8 and/or USB 3.0 ports, Windows installs its crappy drivers, so you should check out this link, posted by the awesome @tommy_riley and try it out for yourselves! Don't forget to drop him a 'Thanks'!
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers <- Courtesy of @tommy_riley!
Wow. Over 40.000 clicks and downloads. I'm amazed at you guys!
It doesn't cost anything or hurt to hit that 'Thanks' button... Please be sure to hit it, it helps me out and also shows me what sort of content you want to see from me.
Do you like the effort I put into this? Then consider donating, by adding towards a new PC: http://www.gofundme.com/NewPC
With a new PC, I can create more one-click solutions and stuff and things!

Updates & other info!! (Reserved)
If you have a problem, I'll do it over TeamViewer, if you wish
Ok, here is some news, for you!
Well, according to some people, who have used this tutorial, Microsoft has done something new to their device driver signing.
I did not have note of this, as I was using Ubuntu most of the time and the laptop I was using broke, several weeks ago (It's gonna take me ages to get a new one, with which I can finally finish my ROM cooking..)
And Senior Member "purpler" has posted a link, which teaches you to turn device driver signing off, in the new bootloader, which Windows 8 is using/will be using, so; let's give him loads of thanks, for this!
here is his answer:
purpler said:
confirmed that it works but i had to diable driver signing from Windows8 bootloader (Shutdown.exe /r /o)
Use and Access Windows 8 Boot Loader and Advanced Boot Options
Click to expand...
Click to collapse
Many thanks to you, purpler!
Please, if you notice anymore changes, which interferes with this method, please let me know, how to solve the problem!
Every helpfull answer, with new solutions will be posted in this thread and thanked many times!
EDIT: If you don't want to donate, but still want to thank me, then use these links, instead of the links, in the tutorial.
Mod edit: No adfly links allowed.
4lex96 said:
I've solve the problem, in stead of usb 3.0 i used a usb 2.0 and it worked! Very strange, with 3.0 i had problem with 2.0 no. I hope this funny thing can help someone.
Best regards
Click to expand...
Click to collapse
Senior member 4alex96 has experienced some problems, while using USB® 3.0 ports.
If you are also experiencing these problems, or you have found a solution to this, be sure to post in this thread or write to me via PM and I'll be sure to quote and write this, so others also get to know and are able to get the most out of there Androids!
Creating a new tool!
Hey guys, I'm going to be creating a new tool or two, which will allow you to install ADB and Fastboot directly to the system root and which will install the Google drivers to your C:\ drive.
These tools will be available for a small donation, and they will save you a lot of work, i.e. you will never have to type in "path=<Whereever the ADB files are>" but you can just debug on
If you want to have the program, hit the "Donate to Me" button on the left of this post and donate a small amount. Then in the donation, write me a message, saying what it's for and give me your XDA username and I'll PM you the download link.
(Minimum of 5€)
tommy_riley said:
For Windows 8, I was having an issue getting my phone to be recognized in bootloader mode on an ASUS laptop that only had USB 3.0 drivers, I followed the procedures at the below URL (luckily I had an INTEL chipset) and once I replaced my native Windows USB 3.0 drivers with the Intel USB 3.0 drivers, I was able to work around a lot of issues:
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
(I cant post HTTP links yet, but you should be able to plug the above into a browser to find the instructions...)
hope this helps!
Click to expand...
Click to collapse
You get that, guys? Go check out that website, and try it out for yourselves!

Tried using this fix keep getting an error saying the driver is not signed.
-Edit
Got it working had to go into advanced boot options and turn off device signing

thisiswar951 said:
Tried using this fix keep getting an error saying the driver is not signed.
-Edit
Got it working had to go into advanced boot options and turn off device signing
Click to expand...
Click to collapse
Ok, cool. I haven't been on my laptop, for a few days, so I wouldn't know, if MS has released any updates, yet...
I was thinking: WTF is he talking about? It's worked by so many people :O...
xD
LG familyguy59

confirmed that it works but i had to diable driver signing from Windows8 bootloader (Shutdown.exe /r /o)
Use and Access Windows 8 Boot Loader and Advanced Boot Options

Hi, I'm using win8 pro 64bit rtm.
when I double click on the UsbDrv.exe from Samsumg nothing comes up.
even when I run it in compatibility mode it doesn't help...
any ideas? I have disabled signed drivers.
thanks!

hshen45 said:
Hi, I'm using win8 pro 64bit rtm.
when I double click on the UsbDrv.exe from Samsumg nothing comes up.
even when I run it in compatibility mode it doesn't help...
any ideas? I have disabled signed drivers.
thanks!
Click to expand...
Click to collapse
You'll have to wait a moment, the system has to look for all the needed files, in the exe, and then needs to try to execute. If it then doesn't work, I'll upload an updated version, but as this seems to be working pretty much fine, I'll hesitate, not that the updated verison causes problems.
Anyways, I was running Win8 64x and it worked fine, just let the computer do it's work and it will work sooner or later, if nothing happens, even after waiting for 5-10 minutes, then try running it with administrative rights (Run as administrator).. Let me know if it works!

Doesn't work for me because I cant even see my S3 in the device manager.

leeznon said:
Doesn't work for me because I cant even see my S3 in the device manager.
Click to expand...
Click to collapse
Then try a different computer Doesn't mean that your S III is kaputt, does it?
If it then doesn't work, you've probably got dirt in the socket, or something else, like that.
And if you don't have dirt in the socket, then I don't know, whats wrong, but it'll definitely go over warranty

I have find an easiest way to install adb driver on windows 8 : ( disabling driver signature )
- after BIOS on "choose Operating system" screen
-clic "change default setting"
-clic "choose other option"
-clic "troubleshoot"
-clic "advanced option"
-clic " startup setting"
-clic on "restart"
-Install the driver adb as if you were on Windows 7 :laugh:

dalien26 said:
I have find an easiest way to install adb driver on windows 8 : ( disabling driver signature )
- after BIOS on "choose Operating system" screen
-clic "change default setting"
-clic "choose other option"
-clic "troubleshoot"
-clic "advanced option"
-clic " startup setting"
-clic on "restart"
-Install the driver adb as if you were on Windows 7 :laugh:
Click to expand...
Click to collapse
That's what the link in the first post is for. And you still need to follow the steps in the tutorial, otherwise it won't work properly.
I know the tutorial looks complex, but it isn't. You just need to read properly
LG familyguy59/Beatsleigher
EDIT: It's spelled "click"

help me to connect android in win 8
Please help me i am not expert I will give my teamviewr password. i spent hole to connect my android to win 8 but not succeed. when you come to online just inform me. many thanks those were helping.

netbook said:
Please help me i am not expert I will give my teamviewr password. i spent hole to connect my android to win 8 but not succeed. when you come to online just inform me. many thanks those were helping.
Click to expand...
Click to collapse
OK, I will be back, tomorrow. I'm currently at a friend's, so I will be back tomorrow. Send me an e-mail, when you're back, and I'll help you, right away!
LG familyguy59/Beatsleigher

familyguy59 said:
Hello!!​
First off; This is copied, from my thread, in the Galaxy Nexus forum... Sorry, if you find the words "Galaxy" or "Samsung". But, this works for pretty much every phone, (except, for the USB drivers)...
So, give it a go...
I haven't found another tutorial, like this at all... So, if you find something like this it's copied from me
Now, on to the actually interesting stuff ^^
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Note: If you feel more comfortable using the Windows Power Shell, you can use that aswell, it is, afterall, only the Windows shell
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... :
Code:
[B][COLOR="Cyan"]devmgmt.msc[/COLOR][/B]
Now, the device manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here
To prevent confusion: When I say install, it can mean unpack, or install... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed) (Thanks so much for 5k+ downloads!!)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has popped up, choose "Browse my computer" and goto your desktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check my root helper out, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your Android Device!!!!
Thanks a ton for 6k+ views/downloads!! The thanks are also very much appreciated!!
9K+ views!!
15K+ views!!!
Click to expand...
Click to collapse
Thanks!!!!! You have no idea how you helped me! Now I don't haveto dual boot Win7 just for this purpose! Thanks a ton!!

llsiddhantll said:
Thanks!!!!! You have no idea how you helped me! Now I don't haveto dual boot Win7 just for this purpose! Thanks a ton!!
Click to expand...
Click to collapse
I'm always glad to help, dude
LG familyguy59/Beatsleigher

heads up - driver signature enforcement policy on win8 can cause some problems. i just disabled it.

shaolinx said:
heads up - driver signature enforcement policy on win8 can cause some problems. i just disabled it.
Click to expand...
Click to collapse
We're already aware of that (see post #2) but still thanks for briefing everyone again.
LG familyguy59/Beatsleigher
Cyanogenmodded very skankily via XDA app. Skanky, indeed

Hi
i try to do this from yesterday night (maybe from 3 o'clock) and nothing... I've windows 8 64bit and xperia S with ICS. With windows 7 i haven't problem but with windwos 8...
Can you help me trought teamviewer?
Thanks a lot dude!

4lex96 said:
Hi
i try to do this from yesterday night (maybe from 3 o'clock) and nothing... I've windows 8 64bit and xperia S with ICS. With windows 7 i haven't problem but with windwos 8...
Can you help me trought teamviewer?
Thanks a lot dude!
Click to expand...
Click to collapse
Well, not at the moment, but I'll get back to you, as soon as I can!
But, to save time, when I'm on your PC, could you make sure you have the executables (ADB, fastboot and the DLLs) from the first post and your OEM USB drivers? That saves a heck of a lot of time
LG familyguy59/Beatsleigher

familyguy59 said:
Well, not at the moment, but I'll get back to you, as soon as I can!
But, to save time, when I'm on your PC, could you make sure you have the executables (ADB, fastboot and the DLLs) from the first post and your OEM USB drivers? That saves a heck of a lot of time
LG familyguy59/Beatsleigher
Click to expand...
Click to collapse
I've solve the problem, in stead of usb 3.0 i used a usb 2.0 and it worked! Very strange, with 3.0 i had problem with 2.0 no. I hope this funny thing can help someone.
Best regards

[Q] Trouble with fastboot

Hi all,
I had a nice, long, detailed post typed out but then my browser at work crashed, so here is the revised edition:
I recently (three days ago) bought a TF300T tablet. Absolutely love it. As any android fan does, I immediately wanted to root it to get the full benefit of the device. I followed the step-by-step guide on the cyanogenmod wiki and have been successful (after a few hours of figuring things out) in unlocking the device. I am aware at this point that my device is unlocked and my Asus warranty is voided. I am also aware I may have to follow different steps to root it, and am willing to do so accordingly.
I'm not set on using cyanogenmod, but that seems to be the most popular and well-known one so I'd like to use one that is established.
So, up until now I have followed that guide but I am having an issue with flashboot. When I go to do the 'fastboot devices' command, I get nothing. It just jumps to the next line, as if I sent a blank command. When I type 'adb devices' it works fine and shows some letters&numbers so I know my device is recognized.
With all that being said, can anyone advise me on which step I'm doing wrong, if any?
Also, I'm -really- cautious about potentially bricking this thing. I still have 30 days at Best Buy but I'm also an employee there and my co-workers know I'm trying to root so if I brick it, it may not be as easy to return it as with a normal customer. I also have the Accidental Damage & Handling plan so if I DO brick it, I can smash it and get a new one without too much incident, if it comes down to it (which obviously is a LAST resort)
My device is as following:
Asus Transformer Pad TF300T unlocked, firmware .29.
I' have about 15 tabs open in Google Chrome right now after SEARCHing the forums, specifically the TF300 forum, and I'm filtering through all the posts right now. If I find a solution I will post asking for this thread to be deleted.
I'm very tech-savvy, but completely new to android. I don't own a smartphone, and this is my first android device, so this is an incredible learning experience. If anyone feels so kind, could you please explain the different terminiologies used in the rooting scene? I hear stuff about blobs, .build files, DE, WW, US stuff. What's what? And what does it all mean?
Thanks so much, and here's to hoping my computer doesn't crash as soon as I press "post"!!
-Opethfan89
*edit* Forgot to add that when I use the command
fastboot flash recovery recovery-clockwork-5.5.0.4-tf300t.img
Click to expand...
Click to collapse
the command prompt just stays stuck on "waiting for device", while my device is stuck on "Starting fastboot USB download protocol"

Slight resolution
So I am just posting with a slight update to what I've been trying to get this working. I uninstalled the ADK, all drivers, and started over from scratch. I installed ADB using the method listed on the CyanogenMod wiki, and it works fine (I can use all ADB commands from command prompt and it lists my device when I use the 'adb devices' command.
So I'm continuing to follow the steps on the CyanogenMod wiki page and I get back to the part about Fastboot. I boot into fastboot mode, plug the device in, and the new development is that my computer DOES recognize fastboot only in device manager. I do have a yellow exclamation mark near it meaning I don't have the proper driver installed.
So now my newest question is, how do I install the driver for -just- fastboot, or where can I find the .inf file so I'm able to install it myself?
I'm SO close to rooting this device I can just taste it!! Any device is very much appreciated
Thanks!
Opethfan89

Are you following this guide?
http://forum.xda-developers.com/showthread.php?t=1668173
Pretty easy to follow and the easiest way to install recovery and root device.

Yes I have followed that guide and like I said I get to the step where fastboot SHOULD be recognized by my computer but it isn't. It shows up in my device manager with a yellow exclamation point so I literally just need the driver to make things work and I should be rooted.

This thread has the drivers you need: http://forum.xda-developers.com/showthread.php?t=1661653
There are no special fast boot drivers. Just install the Asus drivers, and you'll be good to go.
Also, I know this is off-topic, and I mean no offense to you, but every time I see a thread about driver problems in Windows, I feel a thousand times better about using Linux. No drivers to install. It just works.

Have you tried to see the index on tf300t development?
Hope you have all you need and all process.
For Fastboot : [GUIDE] Help for flash more faster when you use Fastboot Line Command
And for Drivers:
ASUS Android USB Drivers.zip - 2012/04/13 - MD5 Sum: 43af8f39ed421caabecd6c4a2de17212 - Size: 8.28 MB (8687221 bytes)
ASUS Pad PC Suite (PC version V1.0.41) - MD5 Sum: 02d7661affefeb0ae05f577b6b24b37a - Size: 145.09 KB (148570 bytes)
ASUS Sync V1.0.82 - MD5 Sum: a7d229ee2f2678819e6a99711d1f572d - Size: 62.18 MB (65195236 bytes)
You will find all you need for your TF300t in this index

As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem

vel0city said:
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
Click to expand...
Click to collapse
You don't need to use android sdk except if you to use commands line.
Use the guide about [URL "http://forum.xda-developers.com/showpost.php?p 27218675&postcount 20"][GUIDE] Help for flash more faster when you use Fastboot Line Command[/URL] and you will see than it's easy and faster to push something
I haven't use android sdk though it's installed on my laptop

philos64 said:
You don't need to use android sdk except if you to use commands line.
Use the guide about [URL "http://forum.xda-developers.com/showpost.php?p 27218675&postcount 20"][GUIDE] Help for flash more faster when you use Fastboot Line Command[/URL] and you will see than it's easy and faster to push something
I haven't use android sdk though it's installed on my laptop
Click to expand...
Click to collapse
I think you do need to install android sdk because of the fastboot files are in there and need it to use fastboot that could be the reason why his computer does not recognize the tablet when he is in fastboot mode. If you look at your android manager you will see a file under android tools that fastboot files are installed.

you need to specify device id
fastboot -i 0x0b05 flash recovery recovery-clockwork-5.5.0.4-tf300t.img
Click to expand...
Click to collapse
try that op

IT WORKED!!!!
EndlessDissent said:
This thread has the drivers you need: http://forum.xda-developers.com/showthread.php?t=1661653
There are no special fast boot drivers. Just install the Asus drivers, and you'll be good to go.
Also, I know this is off-topic, and I mean no offense to you, but every time I see a thread about driver problems in Windows, I feel a thousand times better about using Linux. No drivers to install. It just works.
Click to expand...
Click to collapse
See, I think that's where I messed up. None of the guides say to download ASUS' drivers, and in my anxiousness to root I must have overlooked that step. I will try this today and post my results accordingly!! Also, no offense taken by the linux comment, and I've used linux in the past, but I've had quite a few times where it doesn't "just work" (Like using a broadcom wireless card on my old laptop. I had to learn how to use ndiswrapper and whatnot, not a pleasant experience for a linux newb at that time!!)
I recently removed my Linux partition (was using ubuntu 10.10 because I hate unity!!) and can re-install it if it will make my rooting process easier?
vel0city said:
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
Click to expand...
Click to collapse
Yea I didn't download the asus pad suite drivers, and I think that is what is causing my issue. I wish I could post links to the guides I am following but none of them specify that. They just say to download the android SDK and all drivers are included.
FlyingPoo said:
you need to specify device id
try that op
Click to expand...
Click to collapse
I did do that, flyingpoo. At one point my cmd line showed "Sending file recovery.img (5***kb)" but the tablet never picked it up, so I know there is just some miscommunication between the tablet and the PC. When I typed adb devices in cmd line, I see the device listed, but when I type fastboot devices in cmd line, it just goes to a blank line.
I will try the above listed solutions and hope that something works. Thank you all so much for your help!
*edit* This guy, right here? Yea, he's freakin ecstatic! I installed the drivers from EndlessDissents' post, and it worked!! As soon as I booted into fastboot mode, my computer recognized the device. I then used the command that FlyingPoo used (which I tried in the past), and it showed:
Code:
c:\recovery1>fastboot -i 0x0b05 flash recovery recovery.img
sending 'recovery' <5306 KB>...
OKAY [2.417s]
writing 'recovery'...
OKAY [2.053s]
finished. total time: 4.473s
So now I'm following the next few steps to root it. I've backed up my apps using Astro as well as the ASUS backup suite, and I'm using CWM for a backup of my entire system at the moment.
Thank you again to everyone who responded. I always get hung up on the simplest step, but once that is overcome everything else is a smooth ride downhill

One last noobish question to ask, and then I think I'll be done:
I've downloaded the root-signed.zip file, as well as the latest CyanogenMod file I could find (The official wiki didn't have one listed for any asus products, for some reason?) as well as a google apps for cyanogenmod. I put the files on my SD card but nothing on there is detected within CWM. So the noobish question is which directory do I need to put the files in for CWM to detect it?
That being said, I'm also wanting to backup my system to my external SD card and I selected the option in CWM to backup but it said no sd\ext was detected. Any thoughts?
Thanks again everyone for your responses.
*EDIT* For anyone following this thread, I did figure it out. Another guide I referenced specifies that you copy the files to the INTERNAL SD card (which is kind of confusing, as SD card explicitly refers to an external memory card) and then choose it from CWM. So for me, I downloaded the files on my computer, copied them to my SD card, put the SD card in my tablet, and copied the files to the root directory of the internal storage on my tablet.
Thanks again everyone, I now have root (at least, I'm pretty sure I do?)
Mod, please feel free to close this thread as necessary.

Rooting Double Power (DOPO) M7088 Jelly Bean 4.1.1 Tablet

As always Any information I give is free and this information is to be used at your own risk I take no responsibility for your device this is just my experience and i hope it helps someone with the same problem i had
I recently bought the Double Power (DOPO) M7088 Jelly Bean 4.1.1 Tablet from Walmart.com After a few days of searching and many failed Attempts I finally found out how to root this device and would like to share it to those having the same problem.
After doing some digging i descover the Dopo tablets are nothing more than a rebranded generic rock ship tablets so after some searching here is what i found.
Things you will Need.
1.Pdanet+ for android installer (just type in pdanet+ in your search engine of choice)
2.Your device and usb cable
3.The free download of unlockrootpro (Just type unlockroot into your search engine of choice
Steps.
1. Download and install Pdanet+
2 Download and install unlockrootpro free Version
a. you must be connected to the internet for the installer to work.
b. the unlockroot pro will download a file to your computer that is in itself a down loader it is safe but it does try to get you to install some 3rd part software. if you click the close button it will give you the option to skip the 3rd party software and install just the unlockroot software. it does this 2 or 3 times just click close and skip each time.
3. Connect your Tablet up to the PC and allow all the drivers to install.
4. Once connected start unlockrootpro once it is ope click the green root button it should detect your device and bring up a box just click the button and it will install the root.
a. Now i noticed after it installed the root and say rebooting device my device would not reboot. I unplugged my device and then plugged it right back in and the device immediately rebooted
5. Once your table has rebooted download root checker or the app of your choice to verify root access.
I hope this helped anyone with a Dopo m7088
I don't know if this method will work for any of the other Double Power Tablets so i honestly cannot answer any questions other than what i have stated but feel free to try it if you cannot find any other method.
If this method does Work for you please post a coment on your steps and what device you used this method on so that you can help the community.

M7088
Well i have found out that there is a way to ROOT the M7088 from walmart with out internet connection
Download Moborobo in order to load drivers for the M7088
Just download the same software as you would for the PIPO S1 Its all over the net now and also this M7088 has an attitude about rooting so you might have to click root a couple time to force it to but it does work quite well the Chinese software ( ZhuoDaShi ) after its done you will get a message window in Chinese just copy and paste that text into Google translator and it will tell you ROOT is good Ha Ha ha have fun
backslashx said:
As always Any information I give is free and this information is to be used at your own risk I take no responsibility for your device this is just my experience and i hope it helps someone with the same problem i had
I recently bought the Double Power (DOPO) M7088 Jelly Bean 4.1.1 Tablet from Walmart.com After a few days of searching and many failed Attempts I finally found out how to root this device and would like to share it to those having the same problem.
After doing some digging i descover the Dopo tablets are nothing more than a rebranded generic rock ship tablets so after some searching here is what i found.
Things you will Need.
1.Pdanet+ for android installer (just type in pdanet+ in your search engine of choice)
2.Your device and usb cable
3.The free download of unlockrootpro (Just type unlockroot into your search engine of choice
Steps.
1. Download and install Pdanet+
2 Download and install unlockrootpro free Version
a. you must be connected to the internet for the installer to work.
b. the unlockroot pro will download a file to your computer that is in itself a down loader it is safe but it does try to get you to install some 3rd part software. if you click the close button it will give you the option to skip the 3rd party software and install just the unlockroot software. it does this 2 or 3 times just click close and skip each time.
3. Connect your Tablet up to the PC and allow all the drivers to install.
4. Once connected start unlockrootpro once it is ope click the green root button it should detect your device and bring up a box just click the button and it will install the root.
a. Now i noticed after it installed the root and say rebooting device my device would not reboot. I unplugged my device and then plugged it right back in and the device immediately rebooted
5. Once your table has rebooted download root checker or the app of your choice to verify root access.
I hope this helped anyone with a Dopo m7088
I don't know if this method will work for any of the other Double Power Tablets so i honestly cannot answer any questions other than what i have stated but feel free to try it if you cannot find any other method.
If this method does Work for you please post a coment on your steps and what device you used this method on so that you can help the community.
Click to expand...
Click to collapse

Firmware
Hey awesome i may have a chance to try that method out on my tablet soon if i am lucky. I was wondering if anyone or the one that commented on my original post. I need a copy of the firmware for this tablet mine crashed after lending it out to a friend i am afraid he tried to modify it and somehow corrupted the system it is stuck on the dopo start up screen. if there is anyone who can provide a clean copy of this or even maybe dump a copy of theirs for me i would greatly appreciate it.
.
zxhwk said:
Well i have found out that there is a way to ROOT the M7088 from walmart with out internet connection
Download Moborobo in order to load drivers for the M7088
Just download the same software as you would for the PIPO S1 Its all over the net now and also this M7088 has an attitude about rooting so you might have to click root a couple time to force it to but it does work quite well the Chinese software ( ZhuoDaShi ) after its done you will get a message window in Chinese just copy and paste that text into Google translator and it will tell you ROOT is good Ha Ha ha have fun
Click to expand...
Click to collapse

hey this is great news and I thank you !!!
I was wondering if the m7088 caan be upgraded to CM10/4.2.2?
thanks

I don't know if you can install any form of CM on it as of yet. I have successfully I believe Dumped a copy of the system and recovery images from my M7088. Unfortunately my last unit was toast but being under warrantee i sent it back and they replaced it. Soon as I had it i researched how to back up the system just in case. I can provide my copy of the dump or show the process i used to do it.
I don't know if the dump I have is what is exactly a proper form of back up or recovery. I also don't know what is needed to mod it for CM but at least this is a start to anyone who would like to try.
If there is anyone who would like to and would like the Files I have dumped or any help I can provide let me know. I would like to see Cm/4.2.2 working on this device.

Easy way to root any Dopo tablet
I am not responsible for anything. Use this at your on risk.
Download and install Exynos abuse .
Then Uninstall and get any kind of root checker to verify root access.
And that's it.
Worked for me with no problems. NOW My Dopo tablet is faster than when I got it out the box. With minor tweaking apps and my 32 gb external SD card as my internal SD card and you can find the thread on how to do this on xda forums. Running games like NFS MW, Modern Combat 2 and 3,Nba Jam for android.To run good games like these I had to get a system app freezer like titanium backup to freeze a few useless apps. So now these games run very smooth and flawlessly.Good luck.

backslashx said:
I don't know if you can install any form of CM on it as of yet. I have successfully I believe Dumped a copy of the system and recovery images from my M7088. Unfortunately my last unit was toast but being under warrantee i sent it back and they replaced it. Soon as I had it i researched how to back up the system just in case. I can provide my copy of the dump or show the process i used to do it.
I don't know if the dump I have is what is exactly a proper form of back up or recovery. I also don't know what is needed to mod it for CM but at least this is a start to anyone who would like to try.
If there is anyone who would like to and would like the Files I have dumped or any help I can provide let me know. I would like to see Cm/4.2.2 working on this device.
Click to expand...
Click to collapse
I ran across this post and was wondering if you have the original system and recovery images, as I rooted my M7088 and lost my backup files

m7088 firmware
I am looking for a copy of the firmware for my m7008 tablet.
I am trying to fix a problem of it not starting up its stuck on the DOPO screen.
I believe I can re flash it but DOPO will not send me the file they want me to send in.
Any help will be appreciated.

DOPO logo screen-freeze
putertim said:
I am looking for a copy of the firmware for my m7008 tablet.
I am trying to fix a problem of it not starting up its stuck on the DOPO screen.
I believe I can re flash it but DOPO will not send me the file they want me to send in.
Any help will be appreciated.
Click to expand...
Click to collapse
Joining just to make a couple comments here. I find that DOPO logo screen-freeze seems to be common problem.
My story - This passed Christmas 2012 my son purchased a DOPO M7088 for his 12y/o son, and talked me into a like purchase for myself this past March 2013. Here in Jul 2013, the grandson is visiting with his tablet. When it became frozen with the DOPO screen one night - we tried everything that we could think of to restore. Even pointing fingers at him... to what surprise the following morning my tablet froze updating apps. When I tried to restart, reboot, reset... even tried Vol+/PwrUP, Vol-/PwrUP... allowing the power in the battery to drain to a point that the screen would not light up or flash. Then recharging - nothing worked passed the DOPO screen-freeze.
For reference - I have worked in electronics/computers from the late 60s - so I’m not a rookie here.
Fortunately – I purchased insurance with Wal-Mart, their tech-line made same suggestions as I had done to restore the system, and came to the conclusion that they will completely return/refund my purchase.
Strange that within 12hrs two like tablets crash following app updates, where one is for a young man (games) and the other for adult (general usage). The finger pointing had three other fingers pointing back at us. So apologies to the grandson.
My son may root/re-install the grandson’s system when they return home – for myself I’m going to upgrade to a better brand (now that I'm missing the tablet).
Hope this helps others to understand that the DOPO screen-freeze problem may not be their personal tablet problem but a product problem (I.E. firmware). /TDos

Need dump of 7088 rom
backslashx said:
I don't know if you can install any form of CM on it as of yet. I have successfully I believe Dumped a copy of the system and recovery images from my M7088. Unfortunately my last unit was toast but being under warrantee i sent it back and they replaced it. Soon as I had it i researched how to back up the system just in case. I can provide my copy of the dump or show the process i used to do it.
I don't know if the dump I have is what is exactly a proper form of back up or recovery. I also don't know what is needed to mod it for CM but at least this is a start to anyone who would like to try.
If there is anyone who would like to and would like the Files I have dumped or any help I can provide let me know. I would like to see Cm/4.2.2 working on this device.
Click to expand...
Click to collapse
Hello, I have damaged the ROM by a an installed app after rooting. I see you said that you made a dump of the ROM. If possible, can I get a copy of these files as this would help me greatly. I have rkAndroidTool.exe working. If it works out, I will post the procedure.
Thanks

Dump and Flash the dopo M7088 and other RK3066 based ROMs
Any information I give is to be used at your own risk. I take no responsibility for any damage to your device.
Here's my story: I installed an application to change the fonts after I rooted. This damaged the system and created a boot loop. At this point I had not worked out a reliable method to backup and restore the ROM and in the process of trying to fix, I wound up damaging the partitions trying to push a file back into the tablet with adb.
So in my research to restore the ROM, I came across several methods to flash the ROM, but very few methods to dump the complete ROM and I wanted to be able to extract and restore the entire ROM. In another thread, I found scripts to dump the rk3066 chipset. I expanded this idea and modified the scripts to flash the ROM as well. Also, I created an installer script to simplify the process.
These scripts need to use the Ubuntu Linux live DVD to dump and flash the ROM. The advantages of Linux is you can directly connect to the tablet in flash mode without the trouble of having to install drivers or the android SDK.
Download the Linux 12.04 LTS version from the following Link http://www.ubuntu.com/download/desktop .
Once downloaded, burn this ISO file to a DVD using your favorite DVD burning software. Most burning software have the ability to decode ISO files. If needed, here is a free ISO burner. Link: http://download.cnet.com/ImgBurn/3000-2646_4-10847481.html?tag=mncol;2
Download the attached zip file and copy the zip to the USB drive. Do not decompress in windows as we need to do this under linux to preserve the stored permissions.
Boot the PC from the DVD drive. This should start the Linux. You may need to press an “F” key during the BIOS boot to bring up a menu to select which drive to boot from. You should see a purple screen. This is Linux loading. Select the “Try Ubuntu” option and the Linux should boot to the Linux Desktop.
OK, we are in Linux!
Insert the USB drive into the PC wait for the Linux to open a window. It may take a little bit as we are running off a DVD and some resources need to load. Be patient and watch the light to finish blinking on the USB stick! Drag the “ExtractRomRK3066.zip” file in the USB window to the desktop.
Write down the name of the USB in the title bar of the window.
For example, My USB window says: F490-4740 in the title bar. Write this down, then move the USB window to the side.
Double click on the zip file, this opens the zip in a window. Drag the “ExtractRomRK3066“ folder in the zip window to the desktop. When the copy is finished, close the zip window.
Click on the “Dash Home” icon on the top left of the desktop, Type “Terminal” in the search box and select the terminal application icon.
In the Terminal Window type exactly as shown while observing the caps:
cd ~/Desktop/Ex*
Type the command:
ls -l
You should see a file named “install.sh” along with other commands ending with “.sh”.
Type the line as shown below including the “./”:
./install.sh
The required libraries should install to Linux. Don't worry this is only in memory as we are not installing anything to your hard drive. Make sure everything completed without Errors. If you only see warnings, this is OK!
Let's connect the Tablet to the USB port and put into flash mode. With the Tablet power off and the all cables removed, hold the Vol– button and plug in the USB cable. Continue to hold the Vol- button for 5 seconds. Let go of the Vol- button and connect the power cable. We should now be in flash mode.
We can test if we connected to flash mode by typing:
lsusb
You should see a list of USB devices. Within this list you should see a entry that has the ID:
ID: 2207:300a
If you see the ID, great we are connected to the tablet. If not, make sure the tablet is off and do the above Tablet procedure again.
OK we are connected!
Dumping the ROM
Type the following command replacing the “F490-4740” with your USB name we wrote down earlier from the USB title bar and follow the prompts. This will start the dump of the tablet:
sudo ./dumpall.sh /media/F490-4740/output
YAY! We are dumping the ROM!
Now we wait for “done...”, hopefully without any errors.
Double click on the “ output” folder in the USB drive window.
Verify that we have “backup.img”, “boot.img”, “kernel.img”, “misc.img”, “parm.img”, “recovery.img”, “system.img and userdata.img.
Now in the left panel of the USB window. Click on the ^ icon next to the USB drive description. This will unmount the USB drive for removal.
We are done!
Flashing the ROM
To flash a file you will notice other commands with the extension “.sh”. You may use any of these commands to restore all or part of the ROM.
For example:
To flash the below stock rom, extract the zip file to a USB drive and type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall-user.sh /media/F490-4740/dopo7088stock
To flash a backup of all files including the userdata.img, type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall.sh /media/F490-4740/dopo7088stock
To flash just the recovery, do the same as above only with the command:
sudo ./flashrecovery.sh /media/F490-4740/dopo7088stock
To flash just the system, do the same as above only with the command:
sudo ./flashsystem.sh /media/F490-4740/dopo7088stock
The valid command are:
sudo ./dump?.sh
or
sudo ./flash?.sh
replacing ? With:
all, all-user, backup, boot. cache, kernel, kpanic, misc, recovery, system, user, userdata
----------------------
Hope this helps somebody create a full backup.
Thanks.
UPDATE: I got another dopo m7088 tablet, created a backup using the above method and flashed my bricked m7088 tablet. Everything works again. YAY!
Below is the dumped stock rom for the dopo m7088. Hopes this help's sombody unbrick their tablet.
Extract the dopo7088stk.zip to a USB drive and follow the above instructions.
Thanks
Stock Rom Link: https://docs.google.com/file/d/0B8YnQA1FX-_yUU1ERXh1TjNUbnc/edit?usp=sharing

Thanks
I now have my M7088 again. Thank you . Your instructions where 100% right on.

Partition table not correct in stock M7088 ROM!
After I created the dump of the M7088 ROM and I flashed my tablet, I was looking at the parameter file and realized it was wrong from the factory!
There are several problems that may be the reason some people (including me) has had their devices brick for no apparent reason.
Below is the factory partition table. There is a blank space at address 118000 for a length of 11E000 bytes, this is not a problem. However, the "userdata" partition overruns the "kpanic" and "system" partition as well as the "system" partition overruns the "user" partition. This could lead to data corruption in the partitions.
Factory Partition Table: (length @ start)
[email protected](misc), (2000 + 2000 = 4000)
[email protected](kernel), (4000 + 4000 = 8000)
[email protected](boot), (8000 + 8000 = 10000)
[email protected](recovery), (10000 + 8000 = 18000)
[email protected](backup), (18000 + C0000 = D8000)
[email protected](cache), (D8000 + 40000 = 118000)
(ERROR - Space between 118000 and 236000)
[email protected](userdata), (236000 + 400000 = 636000)
(ERROR - 636000 is past 618000 and 61A000)
0x000020[email protected](kpanic), (618000 + 2000 = 61A000)
[email protected](system), (61A000 + 200000 = 81A000)
(ERROR - 81A000 is past 73A000)
[email protected](user) (73A000 -> end)
It looks like someone made a mistake and/or adjusted the partition sizes and never finished the job!
The only way to fix this is to correct the partition table and re-flash the entire device.
Before I corrected the "parameter" and "parm.img" file, I examined other RK3066 roms as well as the dopo TD1010. The TD1010 has a shorter "system" partition so the fixed partition table below is the same as the TD1010 all the way through the "kpanic" partition.
Fixed Partition Table: (length @ start)
[email protected](misc), (2000 + 2000 = 4000)
[email protected](kernel), (4000 + 4000 = 8000)
[email protected](boot), (8000 + 8000 = 10000)
[email protected](recovery), (10000 + 8000 = 18000)
[email protected](backup), (18000 + C0000 = D8000)
[email protected](cache), (D8000 + 40000 = 118000)
[email protected](userdata), (118000 + 400000 = 518000)
[email protected](kpanic), (518000 + 2000 = 51A000)
[email protected](system), (51A000 + 200000 = 71A000)
[email protected](user) (71A000 -> end)
I corrected the stock firmware and repacked it as dopo7088stkfixed.zip. This file can be flashed with the procedure in the earlier post, replacing the original zip package with this one.
Fixed Firmware Link: https://docs.google.com/file/d/0B8YnQA1FX-_yRmhIN1dCT245R2c/edit?usp=sharing
Also, remember to do a full wipe after flashing.
Thanks
---------- Post added at 02:12 PM ---------- Previous post was at 01:51 PM ----------
putertim said:
I now have my M7088 again. Thank you . Your instructions where 100% right on.
Click to expand...
Click to collapse
No problem. Check my above post. I discovered the partition tables from the factory are wrong which could cause data corruption.
Thanks

i keep on getting this error when trying to reflash i follow the steps i dont know what im doing wrong? ..please help.
[can't open input file 'parm.img': No such file or directory
Error: mkkrnlimg could not decode partition table
[email protected]:~/Desktop/ExtractRomRK3066$

bird56duce said:
i keep on getting this error when trying to reflash i follow the steps i dont know what im doing wrong? ..please help.
[can't open input file 'parm.img': No such file or directory
Error: mkkrnlimg could not decode partition table
[email protected]:~/Desktop/ExtractRomRK3066$
Click to expand...
Click to collapse
Sounds like the path to the files is incorrect.
The command "sudo ./flashall-user.sh /media/F490-4740/dopo7088stock" will look for the media in the path specified.
The "sudo ./flashall-user.sh" is the command part of the line.
The path can be interpreted as "/media/" + "The USB Drive Name in the title bar of the window" + "/" + "The Folder the media is in that has the parm.img file."
For example: if you have the files that includes the parm.img file on the USB drive in a folder called "ROM" and the name of the USB drive at the top of the USB drive window is "ABCD-0123", the line would look like:
sudo ./flashall-user.sh /media/ABCD-0123/ROM
Hope this helps.
{
"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"
}

opening awsfai
mikeopi said:
Sounds like the path to the files is incorrect.
The command "sudo ./flashall-user.sh /media/F490-4740/dopo7088stock" will look for the media in the path specified.
The "sudo ./flashall-user.sh" is the command part of the line.
The path can be interpreted as "/media/" + "The USB Drive Name in the title bar of the window" + "/" + "The Folder the media is in that has the parm.img file."
For example: if you have the files that includes the parm.img file on the USB drive in a folder called "ROM" and the name of the USB drive at the top of the USB drive window is "ABCD-0123", the line would look like:
sudo ./flashall-user.sh /media/ABCD-0123/ROM
Hope this helps.
Click to expand...
Click to collapse
:good: I figured it out. thank you. I have another question what are the proper steps after flashing a new rom? I followed all your steps from dumping to flashing the new fixed rom, but cant get the device out of that stupid DOPO screen. After flashing with the new rom do you unplug it and reboot? BTW its not rooted. thanks

bird56duce said:
:good: I figured it out. thank you. I have another question what are the proper steps after flashing a new rom? I followed all your steps from dumping to flashing the new fixed rom, but cant get the device out of that stupid DOPO screen. After flashing with the new rom do you unplug it and reboot? BTW its not rooted. thanks
Click to expand...
Click to collapse
Hold the power key for about 15 seconds to force a shut down.
After shutting down, do you still get a stuck dopo screen?
If so, try a different USB port on the PC and try the procedure again. Sometime it does not seem to always take.
Make sure you are using the command sudo ./flashall.sh with the fixed rom. For the fixed rom to work, you have to flash all partitions. Then do a factory reset once it is fully booted.
Also, do a wipe. With the power off, hold the vol- and power key. This should bring you into the recovery menu. Do a wipe cache & wipe data/factory reset & reboot.

I have tried your technique at least 4 times and it doesn't work. I can't get through the Linux part with the downloaded file that you offer in your post. I get errors and I cannot go any further.
Either the file that you posted is not good or there is something else going on here. Any idea's? I have also seen other posts saying they cannot get past the errors.

mvalent000 said:
I have tried your technique at least 4 times and it doesn't work. I can't get through the Linux part with the downloaded file that you offer in your post. I get errors and I cannot go any further.
Either the file that you posted is not good or there is something else going on here. Any idea's? I have also seen other posts saying they cannot get past the errors.
Click to expand...
Click to collapse
Please give me more info on what the errors are and what command are they after?

mikeopi said:
Any information I give is to be used at your own risk. I take no responsibility for any damage to your device.
Here's my story: I installed an application to change the fonts after I rooted. This damaged the system and created a boot loop. At this point I had not worked out a reliable method to backup and restore the ROM and in the process of trying to fix, I wound up damaging the partitions trying to push a file back into the tablet with adb.
So in my research to restore the ROM, I came across several methods to flash the ROM, but very few methods to dump the complete ROM and I wanted to be able to extract and restore the entire ROM. In another thread, I found scripts to dump the rk3066 chipset. I expanded this idea and modified the scripts to flash the ROM as well. Also, I created an installer script to simplify the process.
These scripts need to use the Ubuntu Linux live DVD to dump and flash the ROM. The advantages of Linux is you can directly connect to the tablet in flash mode without the trouble of having to install drivers or the android SDK.
Download the Linux 12.04 LTS version from the following Link .
Once downloaded, burn this ISO file to a DVD using your favorite DVD burning software. Most burning software have the ability to decode ISO files. If needed, here is a free ISO burner. Link:
Download the attached zip file and copy the zip to the USB drive. Do not decompress in windows as we need to do this under linux to preserve the stored permissions.
Boot the PC from the DVD drive. This should start the Linux. You may need to press an “F” key during the BIOS boot to bring up a menu to select which drive to boot from. You should see a purple screen. This is Linux loading. Select the “Try Ubuntu” option and the Linux should boot to the Linux Desktop.
OK, we are in Linux!
Insert the USB drive into the PC wait for the Linux to open a window. It may take a little bit as we are running off a DVD and some resources need to load. Be patient and watch the light to finish blinking on the USB stick! Drag the “ExtractRomRK3066.zip” file in the USB window to the desktop.
Write down the name of the USB in the title bar of the window.
For example, My USB window says: F490-4740 in the title bar. Write this down, then move the USB window to the side.
Double click on the zip file, this opens the zip in a window. Drag the “ExtractRomRK3066“ folder in the zip window to the desktop. When the copy is finished, close the zip window.
Click on the “Dash Home” icon on the top left of the desktop, Type “Terminal” in the search box and select the terminal application icon.
In the Terminal Window type exactly as shown while observing the caps:
cd ~/Desktop/Ex*
Type the command:
ls -l
You should see a file named “install.sh” along with other commands ending with “.sh”.
Type the line as shown below including the “./”:
./install.sh
The required libraries should install to Linux. Don't worry this is only in memory as we are not installing anything to your hard drive. Make sure everything completed without Errors. If you only see warnings, this is OK!
Let's connect the Tablet to the USB port and put into flash mode. With the Tablet power off and the all cables removed, hold the Vol– button and plug in the USB cable. Continue to hold the Vol- button for 5 seconds. Let go of the Vol- button and connect the power cable. We should now be in flash mode.
We can test if we connected to flash mode by typing:
lsusb
You should see a list of USB devices. Within this list you should see a entry that has the ID:
ID: 2207:300a
If you see the ID, great we are connected to the tablet. If not, make sure the tablet is off and do the above Tablet procedure again.
OK we are connected!
Dumping the ROM
Type the following command replacing the “F490-4740” with your USB name we wrote down earlier from the USB title bar and follow the prompts. This will start the dump of the tablet:
sudo ./dumpall.sh /media/F490-4740/output
YAY! We are dumping the ROM!
Now we wait for “done...”, hopefully without any errors.
Double click on the “ output” folder in the USB drive window.
Verify that we have “backup.img”, “boot.img”, “kernel.img”, “misc.img”, “parm.img”, “recovery.img”, “system.img and userdata.img.
Now in the left panel of the USB window. Click on the ^ icon next to the USB drive description. This will unmount the USB drive for removal.
We are done!
Flashing the ROM
To flash a file you will notice other commands with the extension “.sh”. You may use any of these commands to restore all or part of the ROM.
For example:
To flash the below stock rom, extract the zip file to a USB drive and type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall-user.sh /media/F490-4740/dopo7088stock
To flash a backup of all files including the userdata.img, type the command changing the “F490-4740” to the name of your USB drive:
sudo ./flashall.sh /media/F490-4740/dopo7088stock
To flash just the recovery, do the same as above only with the command:
sudo ./flashrecovery.sh /media/F490-4740/dopo7088stock
To flash just the system, do the same as above only with the command:
sudo ./flashsystem.sh /media/F490-4740/dopo7088stock
The valid command are:
sudo ./dump?.sh
or
sudo ./flash?.sh
replacing ? With:
all, all-user, backup, boot. cache, kernel, kpanic, misc, recovery, system, user, userdata
----------------------
Hope this helps somebody create a full backup.
Thanks.
UPDATE: I got another dopo m7088 tablet, created a backup using the above method and flashed my bricked m7088 tablet. Everything works again. YAY!
Below is the dumped stock rom for the dopo m7088. Hopes this help's sombody unbrick their tablet.
Extract the dopo7088stk.zip to a USB drive and follow the above instructions.
Thanks
Stock Rom Link:
Click to expand...
Click to collapse
I have tried this today about 8 times today. 4 with each folder you supplied in every usb port on my computer. I could do it all the way down to the dumping. I couldn't get any of the flashing working and my m7088 tablet is still stuck on the dopo screen. Please help as I would like to have this tablet working for my way home in a week.
I have Linux as a second os on my laptop so the first part was easy.
Thanks for your help so far. Good info

[Guide] How to Root LG v10 - Easy [1 Jan 2016]

Root Guide for the T-Mobile LG V10
Read Post #2 - Great Info​
Before we start, I like to mention that I did not create any of these files and I do not take credit for the work done. All I am doing is putting everything in one place and some helpful things that I had to google. This effort is mainly to make the process easier and more efficient as opposed to having to have several tabs or windows open to do it. I will make sure the proper thanks are given at the bottom
Click to expand...
Click to collapse
Instructions Start Here:
Warning - This will erase user data so you will have to set everything back up again! Always BACK UP YOUR DEVICE!!
1. Download the following tools for this process: adb-setup-1.4.3.exe, & twrp-2.8.7.1-h901.img, & UPDATE-SuperSU-v2.46.zip
Alternative ADB and Fastboot Option - (I Prefer) [GUIDE] Install Android SDK Standalone [ADB][30 Dec 2015] for Android SDK Standalone if you are interested
2. Install adb-set-up-1.4.3.exe to install the universal adb driver (Creates adb folder in C:\ if you don't already have adb setup)
3. Go to settings, about phone, software info and tap build number 5x to enable Developer Options
4. Check the Enable OEM unlock box to enable OEM Unlock
5. Enable USB debugging
6. Plug phone into the computer
7. Click on USB options on the phone and change it to PTP (USB Debugging will connect - Authorize Your Computer when prompted from phone)
Screenshots of Enabling USB Debugging and OEM Unlock
1.
{
"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"
}
2.
3.
4.
5.
6.
7. Open a Command Window and change directory to
Code:
[B]C:\adb[/B]
or if you have Android SDK type this below
Code:
[B]C:\Android\platform-tools[/B]
and type
Code:
[B][SIZE="3"]adb devices[/SIZE][/B]
8. You will Get Prompted after adb runs - Allow USB Debugging
8. From the Command Prompt, verify adb sees the device connected -
Open Command Prompt
Code:
cd C:\adb
Code:
adb devices
9. Reboot into the bootloader in command prompt by typing: adb reboot bootloader
10. You will now unlock the bootloader, verify, and Install TWRP
Note* - Make sure you copied twrp-2.8.7.1-h901.img into the C:\adb Folder already
Code:
[SIZE="3"]fastboot oem unlock
fastboot getvar unlocked
fastboot reboot-bootloader
fastboot flash recovery twrp-2.8.7.1-h901.img
fastboot boot twrp-2.8.7.1-h901.img[/SIZE]
11. You should be in TWRP Currently.
12. Reboot the device, it will delete user settings, so you need to repeat steps 3-8 to get adb set-up again
13. Now place UPDATE-SuperSU-v2.46.zip om your phone
14. Reboot into recovery
15. Back up YOUR EFS PARTITION
16. Wipe Cache and Dalvick Cache 3x
17. Flash UPDATE-SuperSU-v2.46.zip
18. You have successfully Unlocked the bootloader and Rooted your Device!!
19. SuperSU will prompt you to give tmobile.pr.adapt root privlidges, DENY
20. Navigate with Root Explorer to /system/priv-app/AdaptClient and rename AdaptClient.apk to AdaptClient.apk.bak and reboot
21. Finally, All done
Click to expand...
Click to collapse
USEFUL ROOTING LG V10 - by: Glenn Silvasy
Give Thanks To:
@KAsp3rd - http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740
@Chainfire - For Super User
@mikeyinid - Flashable Stock Image
@TheJesus - Providing img files for stock ROM, and OEM unlock Guide
@Snoop05 - ADB Drivers and Fastboot
And Anyone else that was missed!

Updated [31 Dec 2015]
References, Guides and Great Information - Please Read​
LG-H901 Stock .img Files (Boot, System, and Recovery)
Go Here
LG-H901 Stock Flashable ZIP in TWRP
Go Herehttp://forum.xda-developers.com/lg-v10/development/lg-h901-stock-images-device-restore-t3241170http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-images-device-restore-t3241170
TWRP
Go Here
ADB and Fastboot
Go Here #1
Go Here #2 - This can be reached from Go Here #1, but I posted it for a direct link to the tool just in case you miss it!
Android SDK Standalone Tools for ADB and Fastboot Devlopment Setup Guide
Go Here
Can't Get Into the Bootloader - Enter Fastboot Mode
Go Here
These links will have all the files you need in case you encounter any issues and I will also try to answer any questions within the scope of my knowledge. I been doing this for a while and there are tons of smart people on XDA. Please search for the question you want to ask to avoid issues, however, I do not believe in biting someones head off either. Researching is how you learn!! :good:

16. Wipe Cache and Dalvick Cache 3x
Click to expand...
Click to collapse
You seriously do not need to do that, this isn't 2010. In fact, if you ever do that when Xposed is installed, you'll cause a bootloop.

siraltus said:
You seriously do not need to do that, this isn't 2010. In fact, if you ever do that when Xposed is installed, you'll cause a bootloop.
Click to expand...
Click to collapse
Actually never caused a bootloop period...at worse it optimized all the apps installed which takes time, but hey thanks for the uneeded criticism
Edit: Also good thing xposed is not even a factor anyway. Sometimes you can not help being ignorant
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Actually never caused a bootloop period...at worse it optimized all the apps installed which takes time, but hey thanks for the uneeded criticism
Edit: Also good thing xposed is not even a factor anyway. Sometimes you can not help being ignorant
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
I'm opening my prompt within the folder adb installed to (C:\adb), adb devices command isn't finding anything. I have the necessary things ticked in developer options. Driver issue maybe? thanks

I never did numbers 15, 16 & 20. Not even sure what number 20 is for. Care to explain?

baySF said:
I never did numbers 15, 16 & 20. Not even sure what number 20 is for. Care to explain?
Click to expand...
Click to collapse
Your EFS partition contains your IMEI number and modem partition that allows you to connect to LTE and data services. This happens on Samsung devices, although rare, it does happen. It is good to just back it up just in case you flash and something happens to that partition, your phone essentially becomes a paper weight. I have always wiped cache and dalvick before flashing anything, feel free to do it if you like, not required.. Lastly, when you have root, that app is a T-Mobile app trying to request root permissions, do not allow it. It is an uneeded app. The only useful T-Mobile apps are the Visual Voicemail, Mobile Hot Spot and T-Mobile My Account.

sleekgreek said:
I'm opening my prompt within the folder adb installed to (C:\adb), adb devices command isn't finding anything. I have the necessary things ticked in developer options. Driver issue maybe? thanks
Click to expand...
Click to collapse
After you unlocked developer settings and checked USB Debugging, did you remember to change your connection from MTP to PTP, once you do that it should prompt you on the phone to allow the connection

bdorr1105 said:
After you unlocked developer settings and checked USB Debugging, did you remember to change your connection from MTP to PTP, once you do that it should prompt you on the phone to allow the connection
Click to expand...
Click to collapse
Yes all checked, I never get the prompt though. Also in the device manager I'm seeing The yellow exclamation for "abd interface". This is such a simple process And I've been jacking with it for awhile. I've run the 15 sec ADB several times already. On windows 10 btw
edit: changing to PTP also

sleekgreek said:
Yes all checked, I never get the prompt though. Also in the device manager I'm seeing The yellow exclamation for "abd interface". This is such a simple process And I've been jacking with it for awhile. I've run the 15 sec ADB several times already. On windows 10 btw
edit: changing to PTP also
Click to expand...
Click to collapse
I am on windows 10, so the adb driver is not installed. Did you run the universal adb driver I have posted in the OP. Run that, then ensure your phone is on PTP. If you still have that yellow exclamation point, right click, uninstall driver, then scan for hardware changes and once the driver is installed correctly, you will be good to go

bdorr1105 said:
I am on windows 10, so the adb driver is not installed. Did you run the universal adb driver I have posted in the OP. Run that, then ensure your phone is on PTP. If you still have that yellow exclamation point, right click, uninstall driver, then scan for hardware changes and once the driver is installed correctly, you will be good to go
Click to expand...
Click to collapse
adb-set-up-1.4.3.exe , yes I've installed that several times. I go to that installed folder (C:abd) and open my command prompt from within it. Maybe I'll just get the sdk again, seems like a real simple issue I can't get sorted. Freaking aggravating

sleekgreek said:
adb-set-up-1.4.3.exe , yes I've installed that several times. I go to that installed folder (C:abd) and open my command prompt from within it. Maybe I'll just get the sdk again, seems like a real simple issue I can't get sorted. Freaking aggravating
Click to expand...
Click to collapse
Well adb wont work unless the driver is working, in device manager, if you have the yellow exclamation point, it wont work. You should have seen the Google ADB driver installer come up like a normal windows program installation. Your driver is giving you problems
Try the attached drivers, just extract the zip and point the computer to look in the location of the extracted folder. See if it makes the exclamation go away

bdorr1105 said:
Well adb wont work unless the driver is working, in device manager, if you have the yellow exclamation point, it wont work. You should have seen the Google ADB driver installer come up like a normal windows program installation. Your driver is giving you problems
Try the attached drivers, just extract the zip and point the computer to look in the location of the extracted folder. See if it makes the exclamation go away
Click to expand...
Click to collapse
Thats a no go also, it's saying windows was unable to install. Thanks for the help, I have to crash though, down to 4 hours sleep before work because of this phone lol. I've never had this issue before, maybe tomorrow I can get it sorted out. thanks again

Running fastboot oem unlock will always wipe your user data

KAsp3rd said:
Running fastboot oem unlock will always wipe your user data
Click to expand...
Click to collapse
Thanks for that info, I am surprised it wipes your data or even touches the user partition. Never would have guessed it was from oem unlock
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Your EFS partition contains your IMEI number and modem partition that allows you to connect to LTE and data services. This happens on Samsung devices, although rare, it does happen. It is good to just back it up just in case you flash and something happens to that partition, your phone essentially becomes a paper weight. I have always wiped cache and dalvick before flashing anything, feel free to do it if you like, not required.. Lastly, when you have root, that app is a T-Mobile app trying to request root permissions, do not allow it. It is an uneeded app. The only useful T-Mobile apps are the Visual Voicemail, Mobile Hot Spot and T-Mobile My Account.
Click to expand...
Click to collapse
Is there a way to check if your IMEI was wiped? I still have data and can still send messages and makes calls but whenever I'm at work, I'll always get "voice access restricted" and I never got that on my nexus 5. I also lose connection to my Wi-Fi at work and at home randomly because it says "avoided poor connection". Granted all I have to do is turn Wi-Fi off then back on but it's very annoying. Again, never happened on my nexus 5.

baySF said:
Is there a way to check if your IMEI was wiped? I still have data and can still send messages and makes calls but whenever I'm at work, I'll always get "voice access restricted" and I never got that on my nexus 5. I also lose connection to my Wi-Fi at work and at home randomly because it says "avoided poor connection". Granted all I have to do is turn Wi-Fi off then back on but it's very annoying. Again, never happened on my nexus 5.
Click to expand...
Click to collapse
If you can access LTE than you are solid.. Trust me you will know, you will get rejected from the network.. It is in settings>about>status it will say 0 or be blank if it missing... Rather be safe than sorry
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Actually never caused a bootloop period...at worse it optimized all the apps installed which takes time, but hey thanks for the uneeded criticism
Edit: Also good thing xposed is not even a factor anyway. Sometimes you can not help being ignorant
Click to expand...
Click to collapse
Clearing Dalvik bootlooped both my G4 and my V10 as well as others with Xposed installed, so I'm passing the warning, no need to be butthurt. Thanks for calling me ignorant, stay classy!

siraltus said:
Clearing Dalvik bootlooped both my G4 and my V10 as well as others with Xposed installed, so I'm passing the warning, no need to be butthurt. Thanks for calling me ignorant, stay classy!
Click to expand...
Click to collapse
I cleared cache and dalvick 3 times after installing xposed, but xposed was updated... Look at how you decided to tell me, in a condescending manner so maybe when I explained my side in the aggressive manner you did which was unnecessary, but anyway, learn to be classy before you ask someone else to be classy. Have a great week and merry Christmas bud
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
I cleared cache and dalvick 3 times after installing xposed, but xposed was updated... Look at how you decided to tell me, in a condescending manner so maybe when I explained my side in the aggressive manner you did which was unnecessary, but anyway, learn to be classy before you ask someone else to be classy. Have a great week and merry Christmas bud
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Aggressive? Condescending? Wow. You need to check your ego at the door, buddy, it gets bruised way too easily.

[GUIDE][ROOT] QLink Serrano 3 (HPP-L55B) Bootloader Unlocking And Rooting Guide

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?