Related
WARNING: IN THE EVENT THAT ANYTHING GOES WRONG, I WILL NOT BE HELD ACCOUNTABLE. I CANNOT STRESS THIS ENOUGH!!!
EDIT: I FORGOT, BEFORE CHANGING RECOVERY OR DOING ANYTHING, ALWAYS DO A NANDROID BACKUP!!!
If you have flashed a custom recovery (clockwork, j_r0dd, etc.) but you want to
1) accept OTA updates but cant do so with the custom recovery
2) send your phone for repair and not void your warranty
3) or UNROOT YOUR PHONE,
it should be easy to revert back to your stock recovery that came with your phone.
NOTE: THIS PROCEDURE WILL ONLY WORK IF THERE IS AN AVAILABLE OTA UPDATE FOR YOUR PHONE!!!
YOU WILL HAVE TO RE-ROOT YOUR PHONE IF YOU WANT ROOT ACCESS AFTER UPDATING! DO NOT RE-ROOT IF YOUR PHONE IS TO BE SENT FOR REPAIR!
Step 1) Download the OTA update. (I have a uploaded a sample update zip at
www . sidsoftinc . com / Blur_Version.0.3.9.MB300.Retail.en.03.zip
*remove the spaces)
Step 2) On completion, the phone should reboot and enter recovery mode, using the custom recovery to update. However, this should fail as most custom recoveries prevent original updates. Note the location of the downloaded update (likely at /cache)
Step 3) Power down the phone and enter into recovery mode manually
Step 4) Using ADB, pull the folder containing the update zip to your computer
Code:
adb pull /**storedlocation**/**nameoftheupdate**.zip update.zip
Step 5) Open the update.zip in your adb folder and look for a file called recovery.img (most likely in system folder)
Step 6) Open up the adb shell and flash the new recovery (recommended)
Code:
adb shell
su
flash_image recovery recovery.img
or you can place it in /system and it will be auto-flashed (not recommended)
Code:
adb push recovery.img /system/recovery.img
Step 7 (if possible) Make it permanent by deleting the custom recovery in /system
Code:
adb shell
cd system
su
mount -o rw,remount /dev/block/mtdblock1 /system
rm recovery.img
mount -o ro,remount /dev/block/mtdblock1 /system
exit
exit
Step 8) Reboot the phone and if you see a triangle warning sign, reboot your phone again. You should see your homescreen before it reboots to install the update again. This time, the original recovery will be used.
Once finished, your phone will be upgraded, unrooted and your applications and data will still be retained.
If you wish to install your previously used custom rom again, you must flash the custom recovery and install the rom, again
If I made a mistake, please do inform me. Thank you
I'm trying to do this for the Tmo G2 and I have reverted using another technique but the clockworkmod is still there. I thought it would get removed!
I have no idea how to get rid of it. Can you give me alittle help?
Did your clockworkmod recovery flash itself into your nv ram. If so then no one can help you there. If you have an ota update and pulled it to your pc, send me a coy and I'll see if I can help you. If you can, send me your ota update zip to [email protected].
Sent from my Motorola Backflip using the XDA App
I'm honestly unsure if it flashed to the nv-ram. Possibly, basically if I do a system boot (power +vol down) and select recovery, it will load the HTC green text with white background then go into clockword recovery. I'm not exactly sure why it still does this.
I used the method on this FORUM THREAD to un-root and get back to stock (using the available files there and method 1-a). I'm just unsure why the clockwork recovery is still there. I'm hoping I can still get back to stock recovery. Possibly I just need to flash the stock recovery.img??
Also, I had some troubles initially with ADB, which is why I used the VISIONary method of rooting. I'd love to try out the gfree method since I believe my ADB is working correctly now and test out some other roms to see what I like the most.
I know you are probably in a different time zone that is way ahead of mine........but can't I just reflash the stock or update ota recovery.img in fastboot mode.......OR is this a bad Idea???
Many users have accidently accepted ota updates on custom rims and recoveries. for fastboot, I did mention that flashing stock recovery and update is possible via adb shell.
Sent from my Motorola Backflip using the XDA App
siidheesh said:
Many users have accidently accepted ota updates on custom rims and recoveries. for fastboot, I did mention that flashing stock recovery and update is possible via adb shell.
Sent from my Motorola Backflip using the XDA App
Click to expand...
Click to collapse
I tried flashing the stock recovery but I'm not sure why it didn't work, I had hboot and flash_image. I used the adb shell way as well. It gave me error in partitions or whatever. I don't know what to do.
do you have Blur_Version.0.3.10.MB300.Retail.en.03.sbf file?
I dont happen to have that file, but i do have Blur_Version.0.3.9.MB300.Retail.en.03.zip
if you need it.
Cockwork Mod
I'm pretty green so this may sound really dumb, but can you flash sbf files to your phone via Clockwork Mod, or does it have to be done via RSD Lite. I cannot get RSD to recognize my device in 4.7 or 4.8. Please help.
do you have a stock image for the huawei ascend for cricket or does anyone here have it?
Unrooting......
I download the RECOVERY file you supplied (thank you)
"Blur_Version.0.3.9.MB300.Retail.en.03.zip"
If I reboot into Recovery and just flashed that zip file, would it work that way to unroot?
Provided you are flashing on a MOTOROLA BACKFLIP, yes. However, you might want to flash the AT&T 2.1 update for the backflip instead, if you reside in the US. Flashing back any official firmware unroots your phone
I'm looking to root and unlock my AT&F Motorola Backflip (MB300).. Any suggestions?
Sent from my NexusHD2 using Tapatalk
OTA for Samsung Galaxy Ace is a CFG file, not ZIP
Hello,
Just for interest, I received an OTA for my Samsung Galaxy Ace but it didn't come as a ZIP file - it came as a CFG file (which is not a ZIP, but actually a proprietary package - which I can't remember the name right now).
However, I did find the stock recovery elsewhere in this forum, and I installed it. But that wasn't enough for the OTA to be installed - it still fails.
Corrupted?
siidheesh said:
Step 5) Open the update.zip in your adb folder and look for a file called recovery.img (most likely in system folder)
Click to expand...
Click to collapse
I can't find it. I have an Alcatel Pop C1 4015X. Help?
Trying to unroot Xperia Z2
I am trying to unroot using update files from the Sony Xperia Companion. I found the update files (I think). I used Flashtool to decrypt the FILESET, but there is no recovery.img in the decrypted folder. The folder I decrypted is in Xperia Companion/Sony Mobile Update Engine/localstorage/db/13740270 and that is the only folder that has decryptable files. They are named FILE_8977018 and similar before decryption and various .sin .ta files (examples auto-boot.ta, cust-reset.ta, simlock.ta). Am I using the right decryption to get the recovery.img?
Hello everybody,
Before telling you about my issue, i should mention that i am a complete newbie regarding flashing kernels. This was my first try, and it didn't work out too well.
I needed to test the USB OTG/Host Functionality for a project at work, and i read that it was possible to enable it on the Nexus S by flashing a custom kernel (kernel_usbhost_build5_icsnexuss from sztupy). It's probably worth mentioning that prior to this i updated the phone to Android 4.0.3.
So i started this morning by rooting it, unlocking the bootloader and installing CWM.
At that point i realized that the recovery mode wasn't accessible : the graphics of the droid with an open belly appears for half a second, and then it gives me the black screen treatment for about a minute before rebooting.
However since there are other ways to flash kernels, i figured i could do without recovery so i didn't look more into it.
I then flashed the kernel using fastboot with this command :
Code:
C:\Program Files\Android\android-sdk\tools>fastboot flash:raw boot H:\data\Downloads\kernel_usbhost_build5_icsnexuss\kernel\zImage
creating boot image...
creating boot image - 3446784 bytes
sending 'boot' (3366 KB)...
OKAY [ 0.422s]
writing 'boot'...
OKAY [ 0.500s]
finished. total time: 0.922s
From the trace i figured that all went well, but when i reboot it stays blocked on the splash screen with the Google logo. Since then i tried flashing several other kernels, without any success. Also tried to flash an update.zip (both ICS and GB) over fastboot but i get this error :
Code:
C:\Program Files\Android\android-sdk\tools>fastboot update H:\data\Downloads\upd
ate.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
So to sum it up i now only have access to the bootloader, without recovery mode.
Before you all jump on me, i know what i did is bad habits (i should have tested the kernel before flashing it), i did it in a hurry without checking i had all sufficient knowledge, and to be honest i would probably have been more careful if was doing it on my personal device.
Truth is now i'm really desperate because i turned my company issued phone into a brick and don't have the slightest idea what to do about it...
Is there any guru out there who knows how i could get out of this ?
Thanks a lot !
Download clockworkmod recovery and use fastboot to flash it.
Fastboot flash recovery yourfilename.img
Enter recovery and mounts and storage and mount USB storage
Transfer the kernel you want to your SD card. The one you flashes isn't a kernel I'm almost sure.
Try a different one.
Then transfer a rom to your SD card.
Factory reset/full wipe, then go to mounts and storage and format everything except your sdcard.
DO NOT FORMAT YOUR SD CARD!!!
Once that is done go to install zip from sdcard and flash the rom and then the kernel and reboot. Should be fine then. Keep me posted.
..
Election Day said:
The image you need would be this ClockworkMod img. Save it somewhere, cd to the sdk/platform-tools/ directory and then do:
Code:
fastboot flash recovery /path/to/saved/file/recovery-clockwork-5.0.2.0-crespo.img
Just drag and drop the file in your terminal, after typing the space after "recovery".
Furthermore, what nodstuff said.
Click to expand...
Click to collapse
Ha ha oops! Forgot that part!
I usually just cd to the one where I have recovery saved!
..
Thanks a lot for answering so quickly !
I'll give it a try on Monday, let you know how it goes.
Election Day said:
Yes, you can also do that, of course. In that case you'd have to provide the full path for fastboot. Or maybe you don't have to on Windows? I don't really use that operating system to be honest.
In that case it would be something like:
Code:
C:\Program Files\Android\android-sdk\tools\fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Looking at OP's quotes that is probably the most logical way in this case, you're right.
Click to expand...
Click to collapse
No I just cd to downloads (where recovery file would be) in terminal, type: fastboot flash recovery xxxxxx img
And that's it.
I set the path to fast boot and adb in environmental variables in device manager.
Maybe that's why.
..
Just tried out your tips, worked like a charm !
However I had to wipe everything twice before it would let me update to 4.0.3, I would get this weird error :
file_getprop: failed to stat "/system/build.prop": No such file or directory
Anyway now I'm back on ICS and, following your advice, i found another kernel to flash : Matr1x. No problem with this one, now I can test USB OTG.
Thanks again, you guys rule !
ABOUT:
This tutorial explains how to use adb to flash the following items starting from a UCLB3 base w/ root.
- Custom kernel w/ CWM recovery
- Modified 3e recovery
- Custom firmware (ROMS)
- Busybox
These instructions will most likely work coming from other rooted Infuse firmwares, but were tested starting from my Odin UCLB3 Unbrick package with root.
ADB SETUP:
Download: adb.zip
Download: SAMSUNG_USB_Driver_for_Mobile_Phones.exe
Setup instructions are for Windows, but adb is also available for Linux and Mac.
a.) If necessary, uninstall any previous Kies or Samsung USB Driver installations, and install the Samsung USB driver from the above download link.
b.) Unzip contents of adb.zip and copy the folder contents to C:\Windows\
c.) If your phone is booted up and running, make sure you select USB debug mode in settings. ADB also works in CWM recovery, and in modified 3e recovery.
d.) To test your installation, open a command prompt (Press WINDOWS KEY + R - type cmd - press Enter).
Type:
Code:
adb devices
If all is working, you will see your device listed.
Some quick command tips:
To move a file from your computer to the phone, "push" it:
Code:
adb push myfile.zip /directory-on-phone/
Of course, you need to be in the computer directory for your file in the command line to push it to the phone.
To get a file from your phone onto your computer, "pull" it:
Code:
adb pull /sdcard/myfile.zip
To access a command prompt for the phone:
Code:
adb shell
Inside that shell, you can use unix commands from within the Android OS to manipulate your phone.
------------------------------------------------------------
INSTRUCTIONS FOR GINGERBREAD:
(Scroll down for ICS Instructions.)
------------------------------------------------------------
Instruction steps must be followed in order.
Step 1: Use adb to install a custom kernel
Download: flash_image.zip (Extract and use flash_image for instructions below.)
You'll also need a Gingerbread kernel zImage.
Code:
adb push flash_image /data/local/tmp/flash_image
adb push zImage /data/local/tmp/zImage
adb shell
$ su
# chmod 755 /data/local/tmp/flash_image
# chmod 755 /data/local/tmp/zImage
# /data/local/tmp/flash_image boot /data/local/tmp/zImage
# reboot recovery
Step 2: Use adb to install modified 3e recovery
Necessary for Step 3.
Download: 3e_recovery_no_sig_check.zip (Extract and use recovery for instructions below.)
Code:
adb remount
adb push recovery /system/bin/recovery
adb shell "chmod 755 /system/bin/recovery"
adb reboot recovery
Step 3: Use adb to install a custom firmware
This step uses the modified 3e recovery to flash unsigned firmware.
You'll need to download the zip file for the Gingerbread (or possibly Froyo) rom that you would like to flash. These instructions have been tested by flashing my Ethereal rom.
Replace YourFirmware.zip with the actual name of your rom zip.
Code:
adb push YourFirmware.zip /sdcard/
adb remount
adb shell
# echo "boot-recovery" > /cache/recovery/command
# echo "--update_package=SDCARD:YourFirmware.zip" >> /cache/recovery/command
# reboot recovery
Let firmware flash complete, and then type:
Code:
adb reboot
EXTRA: Use adb to install busybox
Download: Busybox-1.20.2.zip (Extract and use busybox for instructions below.)
Code:
adb remount
adb push busybox /system/xbin/busybox
adb shell
# chmod 755 /system/xbin/busybox
# ln -s /system/xbin/busybox /system/bin/busybox
# /system/xbin/busybox --install -s /system/xbin
# exit
----------------------------------------
INSTRUCTIONS FOR ICS:
----------------------------------------
STEP: Use adb to flash an ICS kernel; then use blue CWM recovery to install an ICS rom.
Download: flash_image.zip (Extract and use flash_image for instructions below.)
You'll also need an ICS kernel boot.img and it is recommended that you push an ICS rom zip to your sdcard. Once you are in blue CWM recovery, you won't be able to use adb to push anything else to the device.
Replace YourFirmware.zip with the actual name of your rom zip.
Code:
adb push YourFirmware.zip /sdcard/
adb push flash_image /data/local/tmp/flash_image
adb push boot.img /data/local/tmp/boot
adb shell
$ su
# chmod 755 /data/local/tmp/flash_image
# chmod 755 /data/local/tmp/boot
# /data/local/tmp/flash_image boot /data/local/tmp/boot
# reboot recovery
From here, just follow the normal instructions for flashing your ICS rom in blue recovery.
I'll add to these instructions as I find more for ICS, and as support increases for adb in the CWM recovery we're using in ICS roms. At this time, adb support isn't fully working in Infuse ICS CWM recoveries. If you use adb to get an ICS kernel / CWM recovery combination, just use the recovery menu to do anything else. If you need to get other files onto the device while in blue CWM recovery, go to mounts and storage, mount /sdcard/, and mount USB storage.
Hope this is useful to someone else. I mainly wanted to see how much could be done with just adb, and I learned quite a bit about how the phone works in the process.
Wow my friend...nice and thx for what you provide the Infuse Community.
It is people like you, why i stay!
very nice how-to!
bigjoe2675 said:
Wow my friend...nice and thx for what you provide the Infuse Community.
It is people like you, why i stay!
Click to expand...
Click to collapse
SiL3nTKiLL said:
very nice how-to!
Click to expand...
Click to collapse
Thanks fellas. And, by the way, I know that most general users aren't going to use adb to flash kernels and firmware. It's of course easier to use all of the Heimdall one-click and Odin tools that we have - as well as the Infuse Toolkit, Heimdall suite, SGS Kernel Flasher, and CWM recovery. So, for the person asking, "Why would someone still do this, when we have all of the tools that we have?" - this isn't for you.
I approached this from the standpoint of asking, "What if we didn't have access to all of the easy tools?".
At some point, if someone is having issues with Odin and Heimdall, or if they can't use their hardware buttons, maybe they will find this useful. I like to do things from the command line and not have to touch the phone while I'm working on development stuff - plus I type fast, and since I spent years in the command line on Slackware linux, prefer using unix commands. I'm actually faster at CLI stuff than with GUI stuff, plus I like the control that CLI gives you.
I had to help a forum member restore his phone over a remote tech support session using https://join.me/ . He claimed that he couldn't get Heimdall or Odin to recognize his phone. I was able to use adb to do things from his computer, which was helpful, since I couldn't see or directly use his phone. I had to ask him to do some things on the phone, so I later wanted to figure out how to do more using just adb. That's what this is all about. If I had to help someone over a remote session now, I could do most everything without them ever touching their phone.
First of all thank you very much for the guide, but I seem to be having a problem
Whenever I try this:
Code:
adb push YourFirmware.zip /sdcard/
adb remount
adb shell
# echo "boot-recovery" > /cache/recovery/command
# echo "--update_package=SDCARD:YourFirmware.zip" >> /cache/recovery/command
# reboot recovery
the first issue is the phone reboots but continues to system and not to recovery.
now if I manually make it boot recovery, CWM gives me an error that it couldn't mount: SDCARD:update.zip
the update.zip that I'm trying to flash is CM9 RC2, also tried other zip files and also failed.
what am I doing wrong ?!
Thanks in advance.
DeepUnknown said:
First of all thank you very much for the guide, but I seem to be having a problem
Whenever I try this:
Code:
adb push YourFirmware.zip /sdcard/
adb remount
adb shell
# echo "boot-recovery" > /cache/recovery/command
# echo "--update_package=SDCARD:YourFirmware.zip" >> /cache/recovery/command
# reboot recovery
the first issue is the phone reboots but continues to system and not to recovery.
now if I manually make it boot recovery, CWM gives me an error that it couldn't mount: SDCARD:update.zip
the update.zip that I'm trying to flash is CM9 RC2, also tried other zip files and also failed.
what am I doing wrong ?!
Thanks in advance.
Click to expand...
Click to collapse
If you follow the steps correctly from Gingerbread (including the step to install modified 3e recovery), and replace "YourFirmware.zip" with the name of your firmware, these adb commands use 3e recovery to flash firmware. These flashing instructions are not for CWM recovery, and the steps you are following aren't for flashing ICS from Gingerbread. Look further down in the first post for ICS adb instructions.
Sent from my SGH-I997 using Tapatalk 2
jscott30 said:
If you follow the steps correctly from Gingerbread (including the step to install modified 3e recovery), and replace "YourFirmware.zip" with the name of your firmware, these adb commands use 3e recovery to flash firmware. These flashing instructions are not for CWM recovery, and the steps you are following aren't for flashing ICS from Gingerbread. Look further down in the first post for ICS adb instructions.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for clearing it up. The reason why I used that method is because I looked online and I found it on another forum and the post owner didn't mention anything about it should be used with GB.
infuse CM9 rainbows
I'm caught with a half-done CM9 install of the infuse upgraded from cm7.
Somehow I was able too boot once sucessfully into CM9 though with the initial rainbow screen, but now my device hangs in recovery which is also garbled. I've been searching all over for a nice thorough guide to getting this thing going again and your post here was the only one I found remotely applicable to my situation.
I've been trying your ADB instructions for flashing with ICS but I'm stuck at second step: where I only get: cannot stat "flash-image": no such file or directory.
Since I'm stuck in CWM recovery none of the other options seems to see my device, ie. Heimdall or Odin.
Is there a better solution out of my woes?
Excuse my noobiness.
By stucked at recovery you mean it always boots up into recovery (recovery bootloop)?
You should go back to ULCB3 stock, preferably using Jscott's "option C" and flash the GB bootloaders. Then proceed to installing CM9, and remember to do a double flash. (wipes, flash, reboot, phone hangs, boot into cwm with 3-finger combo, wipe and flash!)
This way you'll solve both the recovery bootloop and the rainbows, and bring you CM9
Sent from my sweet and buttery Infuse
andros11 said:
By stucked at recovery you mean it always boots up into recovery (recovery bootloop)?
You should go back to ULCB3 stock, preferably using Jscott's "option C" and flash the GB bootloaders. Then proceed to installing CM9, and remember to do a double flash. (wipes, flash, reboot, phone hangs, boot into cwm with 3-finger combo, wipe and flash!)
This way you'll solve both the recovery bootloop and the rainbows, and bring you CM9
Click to expand...
Click to collapse
Yes the problem right now is that the only understandable thing I get out of the phone is the samsung logo at boot.
I think it goes into recovery but I can't really tell because the screen is garbled. Also using "adb reboot download" seems to make no difference to Odin or Heimdall which both refuse to see the phone.
I would love to find out exactly which state the phone is in but my knowledge of adb isn't that great to say the least.
How do I flash bootloaders using adb only?
I totally appreciate your help Andros, totally out of luck with this so far.
The only way to flash bootloaders is in download mode using either odin or heimdall.
Adb reboot download should get you into download mode as long as you have adb access while on recovery. If not, get into download mode this way:
Take out battery, and put it back in.
Hold both vol+ & vol- (don't press power)
plug in usb cable to phone.
Once in download mode, your phone should be recognized by Odin. If not, try reinstalling the drivers using the ones in the iset thread.
There are many threads about this situation that should also help you out, just search around
Sent from my sweet and buttery Infuse
Okay, somehow I missed how to use the keys to enter download state.
In my mind using adb to enter download state should be the same as the keys but somehow that isn't the case.
Got the GB bootloaders installed and used an odin package and then redid the CM9 installation.
Sorry about spamming this thread, and thanks to andros for getting me going again.
Interesting, I also didn't know that could make a difference. Lesson learned lol
Glad you got it running again
Sent from my sweet and buttery Infuse
hi , i am having serious problem ,
my i997 was ok before after doing a mess , now its in 3e reocvery restarts in samsung logo comes to 3e recovery again and so on.....i did everything ,flashed with I997UCKH1 but all in vain .
Could somebody guide what to do ?
umairrashid1 said:
hi , i am having serious problem ,
my i997 was ok before after doing a mess , now its in 3e reocvery restarts in samsung logo comes to 3e recovery again and so on.....i did everything ,flashed with I997UCKH1 but all in vain .
Could somebody guide what to do ?
Click to expand...
Click to collapse
Use odin or heimdall to repartition back to uclb3 stock.
andros11 said:
Use odin or heimdall to repartition back to uclb3 stock.
Click to expand...
Click to collapse
i used heimdall ,it flashed successfully but still no result .
how to do he same using odin ?
could you please add more steps in order o recover the phone fully .
i am in a big problem .
Pantech Discover P9090 (Magnus) Root & Modification Guide
This thread is intended as an updated version of the original Ultimate Pantech Discover/Magnus/P9090 Rooting & Modding Thread thread. I created this thread to bring the latest knowledge and tutorials to the top. If you are interested in the evolution of Discover rooting and modding pour yourself a cup of coffee, tea, or ??? and review the posts in that thread and when you are ready to modify your Discover come back here.
Available Mods
Root access
ClockworkMod Recovery
TWRP Recovery
Restore unlocked bootloader for Jellybean devices
CWM flashable ROM/partition updates
Warning/Disclaimer
The tutorials posted in this thread at the time of this writing have been tested and should do what they claim to do without causing harm to your phone, however, if for any reason things go awry when doing any kind of update or modification to your phone the authors of these tutorials or thread posts are not responsible. There is always a chance that modifying your phone can cause damage or a loss of features. Proceed at your own risk. I suggest you read the procedure you intend to implement thoroughly and if necessary ask questions before you proceed. Also, installing mods may make it so you cannot receive or install updates from Pantech/AT&T.
Modification Procedure Order
Determine if your device is running Ice Cream Sandwich (ICS) or Jellybean (JB)
Open the Settings app and tap on "About phone"
If the "Android version" is 4.0.4 you are running ICS, if it is 4.1.2 you are running JB
Set up and ensure you have ADB access to the phone
For now you will have to find an ADB installation tutorial elsewhere
Root your device
Follow the tutorial here.
Jellybean (JB) users should revert back to the unlocked (ICS) bootloader to increase the chance of brick recovery
Follow the tutorial here.
Install ClockworkMod Recovery or TWRP
Follow the tutorial here (CWM) or here (TWRP).
(Optional) Install custom ROM(s)
Follow the tutorial here.
Useful links
Pantech Discover Specs
Ultimate Pantech Discover/Magnus/P9090 Rooting & Modding Thread - Not all content is still relevant but a great read
PantechDevTeam Github - The original Pantech devs (a ton of awesome work here)
PantechDiscover Github - Put together by @Unjustified Dev with contributions from @mifl and myself
Pantech Discover Jellybean Kernel Source
Pantech Discover ICS Kernel Source
Thanks to everyone who helped test and provide feedback for these advancements. A big thanks to @Unjustified Dev & @mifl for their continued development help and porting TWRP (Unjustified Dev) and to @ShotSkydiver for creating the original Pantech Discover mod thread.
Root
Rooting the Pantech Discover P9090
WARNING: Please review the Warning/Disclaimer in the original post before following this procedure!
Click "CLICK TO SHOW CONTENT" to proceed.
Users running ICS
Download recovery-magnus.img, su, and SuperSU_1.65.apk and move them to a directory of your choosing hereafter known as <install-directory>
Boot the phone in fastboot (bootloader) mode by holding down both volume buttons and the power button, once the menu appears use the volume buttons to select "fastboot", then hit the power button
Attach your phone to your computer
Open a cmd window (Windows) or terminal/shell (unix flavors) and type the following command (hit enter after each):
Code:
cd <install-directory>
Now boot to the magnus recovery by typing:
Code:
fastboot boot recovery-magnus.img
The phone should be booted to CWM, now type:
Code:
adb push su /sdcard/
adb push SuperSU_1.65.apk /sdcard/
adb shell
You should now be in an adb terminal on the phone, type the following:
Code:
mount /dev/block/mmcblk0p14 /system
cd /sdcard
cp SuperSU_1.65.apk /system/app/
cp su /system/xbin/
chmod 4755 /system/xbin/su
exit
If all goes well you should be back in your computer's terminal, reboot the phone with
Code:
adb reboot
Enjoy!
Users running Jellybean
Download and install the Framaroot app (version 1.6.1 or later) from here.
Install and open the app
Select "Gandalf"
Reboot the phone for good measure
Enjoy!
Bootloader
Reverting to the Unlocked (ICS) Bootloader from the JB Bootloader
WARNING: Please review the Warning/Disclaimer in the original post before following this procedure!
Click "CLICK TO SHOW CONTENT" to proceed.
Context: The Jelly Bean update for the Pantech Discover flashes a locked bootloader over the unlocked Ice Cream Sandwich bootloader. The result is that you can no longer use fastboot to flash images or boot to external bootloaders. If you are on ICS this tutorial does not apply.
You can test to see if you have the locked bootloader by booting into fastboot (power off device, power on devices holding both volume keys, select fastboot), connect the device to your PC, and run the following command from a command terminal.
Code:
fastboot boot recovery-magnus.img
NOTE: If you don't already have the magnus recovery image download it from here.
If your output looks like the message below you have the locked bootloader and this guide applies to you.
Code:
downloading 'boot.img'...
OKAY [ 0.538s]
booting...
FAILED (remote: Not Support !!)
finished. total time: 0.543s
Procedure: If you have the locked bootloader, you would prefer not be locked, and you are willing to take the risk you can follow the procedure below.
Prerequisites
Phone must be rooted
ADB access
Download the ICS bootloader image (aboot.img) from here.
Connect your phone to your PC and from a command window in the download directory type:
Code:
adb push aboot.img /sdcard/
adb shell
If you are connected to your device at this point type:
Code:
su
cd /sdcard
md5sum aboot.img
The output should be:
Code:
7f55c5ab321cf20e595b841371f45cda aboot.img
The MD5 checksum should be the hex number above (beginning in 7f and ending in cda). If it does match download it again and make sure the checksum matches before proceeding. If no matter what you do you can't get a match then don't proceed.
If you are here then you have the ICS bootloader and it's ready to be flashed, before we do this you should check the checksum for the bootloader partition with the command:
Code:
md5sum /dev/block/mmcblk0p5
output:
Code:
8b6fa6881c7f155858243e94490d0a29 /dev/block/mmcblk0p5
If you are on JB the checksum should match mine.
Now you are ready to flash the ICS image. If you are feeling confident and risk adverse run the command below:
Code:
dd if=aboot.img of=/dev/block/mmcblk0p5
You should get the output:
Code:
5120+0 records in
5120+0 records out
2621440 bytes transferred in 0.458 secs (5723668 bytes/sec)
Don't be concerned if the transfer time is not precise.
Now confirm that our checksum is updated to the new image:
Code:
md5sum /dev/block/mmcblk0p5
Code:
7f55c5ab321cf20e595b841371f45cda /dev/block/mmcblk0p5
If not follow the bail out procedure outlined after this procedure, otherwise get back to your PC command window with:
Code:
exit
exit
Reboot into the ICS bootloader with:
Code:
adb reboot bootloader
Once you are in fastboot verify it worked with:
Code:
fastboot boot recovery-magnus.img
You should be rewarded with the following output:
Code:
downloading 'boot.img'...
OKAY [ 0.544s]
booting...
OKAY [ 0.020s]
finished. total time: 0.565s
You are done!!!!!
Invalid checksum: If the checksum you show does not match the checksum above you can reflash the JB bootloader and if all goes well you will be back where you started.
Download the JB bootloader (jb-aboot.img) from here.
Follow the procedure above to push the bootloader to the device and validate that the checksum matches the original JB checksum you copied on step above.
Flash the JB bootloader as per the guide above replacing aboot.img with jb-aboot.img.
If you have problems I strongly suggest you refrain from rebooting your phone and ask for help.
CWM
Installing ClockworkMod 6.0.2.8 on your Pantech Discover
WARNING: Please review the Warning/Disclaimer in the original post before following this procedure!
Click "CLICK TO SHOW CONTENT" to proceed.
Prerequisites
You must have adb and fastboot installed and working on your computer. There are literally hundreds of tutorials on this so I won't go into it here.
Your phone must be rooted
Optional but recommended
If you are on Jellybean and you haven't already done so I recommend reverting to the unlocked (ICS) booloader. An unlocked bootloader will increase the ability to restore a "brick" substantially.
Ready, set, go!
Option 1 (Do this if you have the unlocked ICS bootloader this is much faster)
Download update_magnus_clockworkmod-6.0.2.8.zip and recovery-magnus.img and move them to a directory of your choosing hereafter known as <install-directory>
Turn off the phone, copy update_magnus_clockworkmod-6.0.2.8.zip to a micro sdcard and install it in the phone
Boot the phone in fastboot (bootloader) mode by holding down both volume buttons and power, once the menu appears use the volume keys to select fastboot, then hit power
Attach your phone to your computer
Open a cmd window (Windows) or terminal/shell (unix flavors) and type the following command (hit enter after each):
Code:
cd <install-directory>
Now boot to the magnus recovery by typing:
Code:
fastboot boot recovery-magnus.img
The phone should be booted to CWM, now select the menu options:
install zip from sdcard > choose zip from external sdcard
Select update_magnus_clockworkmod-6.0.2.8.zip then hit power and confirm by choosing
Yes - Install update_magnus_clockworkmod-6.0.2.8.zip
Once the install is finished choose
Go Back > reboot system now
Enjoy!
Option 2 (Do this if you have the locked Jellybean bootloader and do not wish to revert it):
Attach your phone to your computer and make sure it is booted to Android
Download recovery-magnus.img and move it to a directory of your choosing hereafter known as <install-directory>
Open a cmd window (Windows) or terminal/shell (unix flavors) and type the following command (hit enter after each):
Code:
cd <install-directory>
adb push recovery-magnus.img /sdcard/
adb shell
In the adb terminal type:
Code:
cd /sdcard
ls
Verify that the recovery-magnus.img file is there and if so type:
Code:
su
mount -o rw,remount /system
dd if=recovery-magnus.img of=/dev/block/mmcblk0p20
You should see output indicating that the image was flashed (I'll try to update this with the exact text). If you get an error don't continue and when you reboot to Android the original recovery should be restored. Otherwise type:
Code:
mv /system/recovery_from_boot.p /system/recovery_from_boot.p.bak
exit
exit
You should be back in your computers terminal, type:
Code:
adb reboot recovery
You should be in CWM 6.0.2.8 after a minute or so. The first time you reboot CWM will ask if you want to prevent recovery from being overwritten, go ahead and say yes.
You can use the backup feature to backup your ROM.
What works
Backup/restore from sdcard and external sdcard (including advanced restore)
Delete backup (sdcard and external sdcard)
Choose default backup method
Install zip from sdcard (external)
Wipe cache
Wipe dalvik-cache
Wipe data/factory reset
Mounts - mounting and unmounting partitions
Key test
Show log
Fix permissions (I ran this and it completed and the phone boots but I haven't done exhaustive testing so I don't recommend it, shouldn't need this feature at this point)
What hasn't been tested yet
Install zip from sideload
Format partitions (not recommended)
Partition external sdcard
Report error
Bugs
Backups do not reflect the correct date (common issue that can be resolved eventually)
ROM
Flashing a Custom ROM
WARNING: If you downloaded the ROM that was originally linked to in this guide (magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted-all_partitions.zip) please do not flash it!! While this has worked on most phones the original IMEI on a couple of phones was wiped out.
WARNING 2 (Untested fix uploaded on 11/29, see below) : A couple of users have reported that this update failed on their phones but they were able to restore from a nandroid backup. If you still want to try this ROM please backup your current ROM in CWM first! If you try this please let me know if this works or does not work on your phone and which Android version you were on prior to flashing it. Thanks!
UPDATE 11/29/2013 Newly uploaded file will most likely fix the issues mentioned in warning 2 above, however, I still strongly encourage that you do a backup in CWM before flashing. Please respond with the results indicating which version of Android you flashed this over.
Click "CLICK TO SHOW CONTENT" to proceed.
This guide covers the procedure to flash a specific, JB ROM as discussed below, however, the basic procedure can be used to flash different ROMs as they become available.
Features
Jellybean 4.1.2 stock (other than noted below)
Rooted with /system/xbin/su
SuperSU installed as a system app
Magnus CWM recovery
ICS unlocked bootloader (aboot)
This update is intended to install the unlocked bootloader for all users; provide a restore point going forward; and serve as a basis for future ROMs and enhancements.
This update does not flash the cache or data partitions so your installed apps and data will remain.
WARNING: Please review the Warning/Disclaimer in the original post before following this procedure!
NOTE FOR ICS USERS: The AT&T/Pantech OTA JB Update (from ICS) provides patches to several partitions that are not patched as part of this update. If you are able to run the OTA update I recommend it, if not and you don’t mind having a “hybrid” ROM go for it at your own risk.
Since this flashes the bootloader I strongly recommend checking the MD5 Checksum as per the guide below before executing the update. Make sure the device has enough power, and don't unplug, wiggle, or otherwise mess with the device until the update is complete.
Prerequisites
Magnus CWM installed per the guide above (see OP)
Jellbean or ICS (see notes above before flashing over ICS)
ADB installed and functional
Make sure the battery level of the device is adequate
Flash from the internal sdcard
Download the update from here.
Boot into CWM recovery by holding down the volume up button and power button
Do a CWM nandroid backup
Select "mounts and storage > mount /sdcard > +++++Go Back+++++"
Select "wipe cache partition"
Select "advanced > wipe dalvik cache > +++++Go Back+++++"
OPTIONAL: Select "wipe data/factory reset". WARNING: This will remove your personal apps and data!
Once the download from step 1 is complete, plug the phone into your computer, open a command window, navigate to the download directory, and push the update to the sdcard with:
Code:
adb push magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted2.zip /sdcard/
Check the md5 checksum to ensure you don't have a corrupt download (IMPORTANT!)
Code:
adb shell
cd /sdcard
md5sum magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted2.zip
Should result in:
Code:
3dca0555f81cef97e304c17515c807fa magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted2.zip
If not, download the update and try again. Do not proceed if your checksum doesn't match!
Exit adb shell:
Code:
exit
On the phone, select "install zip from sdcard > choose zip from sdcard", select the update file, and confirm
Wait patiently and do not unplug the device or disrupt the process!
When the update is finished select "+++++Go Back+++++" followed by "reboot system now", if you are prompted to "Fix root" select "Yes" to prevent it from warning again
Wait patiently while it boots, configures the apps, compiles & caches, and connects to your carrier. This can take a few minutes.
Enjoy!
Nice guide. Can't wait till this phone comes if I'm not mistaken cogency sent it again
Sent from my SCH-I535 using Tapatalk
Unjustified Dev said:
Nice guide. Can't wait till this phone comes if I'm not mistaken cogency sent it again
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks! I have been pretty swamped at work so I haven't been able to pull your kernel updates but I am anxious to get back to it. I am glad you have a phone on the way.
Great detailed guide, that provides easy to follow instructions.....nice work, again.
CM11.0
gj23 said:
Great detailed guide, that provides easy to follow instructions.....nice work, again.
Click to expand...
Click to collapse
I predict that on 2 months we will get CM11.0 (kitkat) for the p9090
eeter said:
I predict that on 2 months we will get CM11.0 (kitkat) for the p9090
Click to expand...
Click to collapse
I predict less than one month when my Discover comes in
Sent from my SCH-I535 using Tapatalk
I saw in the Original Thread that Updating to Jellybean on an ICS device doesn't work and he made it work by restoring a nandroid backup and then flashing the rom via CWM.
Any other way to directly upgrade to Jelly bean by flashing the zip via CWM directly without using nandroid backup?
Thanks.
vijayr2002 said:
I saw in the Original Thread that Updating to Jellybean on an ICS device doesn't work and he made it work by restoring a nandroid backup and then flashing the rom via CWM.
Any other way to directly upgrade to Jelly bean by flashing the zip via CWM directly without using nandroid backup?
Thanks.
Click to expand...
Click to collapse
If you are talking about the post below I think you misunderstood. Flashing Jellybean using the guide on the first page of this thread worked for him. He was outlining the history of what he has done on the device and nothing worked other than the magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted.zip update.
If you are on ICS and you have CWM installed the guide in post #5 will get you on Jellybean with all of the goodies.
osopol4r said:
Confirmed working....
> ICS Unable to Update
> Updated to JB with nandroid provided here
> JB nandroid missing browser apk
> Restored from to and from previous ICS
> Installed zip from sd card magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted.zip
> Phone booted correctly, so far so good
I'll report back any issued (if any)
Thanks!!!
Click to expand...
Click to collapse
New subforum in "DevsNest Developments" dedicated to Pantech P9090:
http://www.devsnest.com/forumdisplay.php?fid=142
We hope you include some content in it.
Greetings.
sandnap said:
If you are talking about the post below I think you misunderstood. Flashing Jellybean using the guide on the first page of this thread worked for him. He was outlining the history of what he has done on the device and nothing worked other than the magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted.zip update.
If you are on ICS and you have CWM installed the guide in post #5 will get you on Jellybean with all of the goodies.
Click to expand...
Click to collapse
Great! I somehow misunderstood it. I will update after i install. Thank you for your time spent in contributing for Pantech Discover. Kudos!
vijayr2002 said:
Great! I somehow misunderstood it. I will update after i install. Thank you for your time spent in contributing for Pantech Discover. Kudos!
Click to expand...
Click to collapse
If u install the JB 4.1.2 from here that's rooted and CWM you won't need to update as u will be on Jellybean.
was having wifi issues and bluetooth issues and was ics/jb mix . everything flashed fine and updated fine. will post back after further testing but all seems to be working and volume seems a bit better now.
greg97526 said:
was having wifi issues and bluetooth issues and was ics/jb mix . everything flashed fine and updated fine. will post back after further testing but all seems to be working and volume seems a bit better now.
Click to expand...
Click to collapse
Glad to hear it! I have been waiting to hear from you. I am interested to know if this improves your wifi/bluetooth issues.
sandnap said:
Glad to hear it! I have been waiting to hear from you. I am interested to know if this improves your wifi/bluetooth issues.
Click to expand...
Click to collapse
Blue tooth works flawlessly. Still a bit lagging on wifi. Maybe I need to remove the files we added that didn't match up with what you had or did this update erase all of that?
greg97526 said:
Blue tooth works flawlessly. Still a bit lagging on wifi. Maybe I need to remove the files we added that didn't match up with what you had or did this update erase all of that?
Click to expand...
Click to collapse
This update completely wipes /system then copies over all of the stock Jellybean files so there are no remnants of our hand-crafted /system left. The update also flashes all of the Jellybean partitions that were patched as part of the OTA update so your device should now be consistent with those of everyone who has executed this update with the exception of your /data and /sdcard. You could try backing up your applications and doing a factory reset in CWM.
How about that!
Hi there!
I don't know if you remember me from the old post but...
I just realized my IMEI changed, I used to have my pantech discover unlocked (network unlock) and I believe after flashing the Jelly Bean update file some how relocked itself plus the IMEI also changed. I purchased the unlock code and I just compared the IMEI and it is not the same, plus the phone is now network locked.
I'll try my original nandroid backup and see what happens.
This thread is about DL701Q tablet.
Specs uploaded here.
http://www.specdevice.com/showspec.php?id=bcad-973e-0033-c5870033c587
http://www.bestbuy.com/site/digiland-7-8gb-black/8610212.p?id=1219354106671
This is a cheap quad core tablet that includes bluetooth and GPS, Specs http://specdevice.com/showspec.php?id=a1a0-8080-0033-c5870033c587
The tablet's one short cumming is Ram (512 MB), The tablet works well despite the amount of Ram, it uses swap partition to help balance out the lack of Ram.
CWM Recovery now backs up and restores, use caution as with anything you use, you could damage your tablet.
micro sdcard required to use this recovery.
Code:
Do not use format commands at anytime.
format /data
format /cache
format /system
to install
adb reboot bootloader
fastboot flash recovery DL701Q_dual_boot_recovery.img
fastboot reboot
after tablet reboots
adb reboot recovery
unmount cache
mount system
mount data
mount cache
go back
backup/restore
backup
to restore almost same process
adb reboot recovery
unmount cache
mount system
mount data
mount cache
go back
backup/restore
restore
CWM Recovery
download
https://www.androidfilehost.com/?fid=95916177934541508
To root this tablet, use the CWM recovery, I ported to flash SuperSU
download
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Firmware
download
http://www.panduoduo.net/r/9960566
http://www.mediafire.com/download/0au4z5j9leao9ft/mid713l-lp-lvds-20141226.rar
https://mega.co.nz/#!18wVWTRR!sa1ua8cWoczNT6cTdqzBgaqXRyYoyNPzVah_NaZzNcc
If you choose to flash firmware not needed if your tablet is working fine.
I would recommend flashing only system, then flash gapps. This firmware is older than what comes with DL701Q tablets, plus it doesn't include gapps or wifi update. This version can't be updated, so make sure to backup your system before flashing this system.
If DL701Q tablet gets wifi updates you need stock system to get them, so keep a copy of your stock system handy.
Gapps I used pa_gapps-modular-micro-4.4.2-20140608-signed.zip
https://www.androidfilehost.com/?fid=23501681358543824
Below are some pics of battery life and GPS, GPS test taken inside my house, too much snow to go outside. I haven't tried offline maps yet, I have navfree installed on tablet, will test when roads are clear.
Good battery life also.
to flash recovery
enable usb debugging setup adb and fastboot
adb reboot bootloader
or from power off
press power and volume up at same time, when you come to a selection screen use volume up to select fastboot volume down to boot into fastboot.
fastboot flash recovery /path/to/recovery
credits
Carliv
Chainfire
TKruzze
Tested GPS, via navfree usa works great, If you are going to try navfree usa, use older version, the latest version doesn't work very well, lot of bugs, very slow.
I am going to give MapFactor a try today, very lite navigation app.
Added new recovery to OP.
UBIFS filesystems are not as easy to use as ext4,use caution with this type of tablet, I have uploaded a cwm version that backs up and restores, You use this recovery at your own risk.
For the recovery to work correctly the process must be preformed correctly, below is the process that works.
I am sure the question why unmount cache and later remount cache, this is needed cause cache mounts wrong partition during initial start up. I could force cache to mount correct partition, but this is a dual recovery, so it would be counter productive to do that.
Anyway it only takes a few seconds to unmount cache, then mount system, data and cache in that exact order to get recovery to see partitions correctly. DO NOT USE FORMAT COMMAND PERIOD.
EG
format /data
format /cache
format /system
When restoring backup, recovery will wipe partitions, not format them, wipe is all that's needed
micro sdcard required to use this recovery.
Code:
Do not use format commands at anytime.
format /data
format /cache
format /system
to install
adb reboot bootloader
fastboot flash recovery DL701Q_dual_boot_recovery.img
fastboot reboot
after tablet reboots
adb reboot recovery
unmount cache
mount system
mount data
mount cache
go back
backup/restore
backup
to restore almost same process
adb reboot recovery
unmount cache
mount system
mount data
mount cache
go back
backup/restore
restore
On other thread you were working on flashable rom via cwm recovery, how is that going?
tomtom1265 said:
On other thread you were working on flashable rom via cwm recovery, how is that going?
Click to expand...
Click to collapse
Yes, I have two flashable roms, one is made from my tablet dl701q system, other one is made from mid713l system.
They both work well, both roms are ubifs systems, both are rooted and allow adb remount.
Sent from my Venue 8 3830 using Tapatalk
Uploaded specs see OP.
Sent from my DL701Q using Tapatalk
Will this recovery work with other mt8127 tablets? Got a nextbook 7 and I'm interested in making/flashing a custom recovery as safely as possible (I've already exchanged it twice, trying to avoid a third trip) any help would be appreciated
corruption said:
Will this recovery work with other mt8127 tablets? Got a nextbook 7 and I'm interested in making/flashing a custom recovery as safely as possible (I've already exchanged it twice, trying to avoid a third trip) any help would be appreciated
Click to expand...
Click to collapse
I have no ideal, I made this recovery for this tablet, if your tablet is ubifs and partitions and kernel are the same recovery should work, if not it won't.
sent from my kingSing T1 via taptalk
There are two versions of DL701Q tablet.
1. ro.sf.hwrotation=90
2. ro.sf.hwrotation=0
Version 1 has full software on Digiland website.
http://www.digi-land.net/Photo_Show.asp?InfoId=487&ClassId=56&Topid=53
If you have version one you should be able to use software as is, if you have version 2, like I do you will need to edit build.prop else touch screen will be wrong, plus screen will be upside down.
You can flash full software if you want, I only flash system.
this is my method to flash system, once you have downloaded the software unpack it, need to have custom recovery, boot tablet into custom recovery.
Code:
adb reboot recovery
unmount cache
mount system
mount data
mount cache
rm -rf /system/*
rm -rf /data/*
rm -rf /cache/*
adb reboot bootloader
fastboot flash system system.img
power off tablet, or press reset button in back
hold power up + volume up to get into boot selection
choose recovery then tab volume down.
when recovery fully loads.
unmount cache
mount system
mount data
mount cache
adb pull /system/build.prop
change ro.sf.hwrotation=90 to ro.sf.hwrotation=0
adb push build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
reboot
You should now be able to use the software, somethings may be a little off camera and so on but non the less software is usable.
Don't like software use recovery to restore your back up.
vampirefo said:
There are two versions of DL701Q tablet.
1. ro.sf.hwrotation=90
2. ro.sf.hwrotation=0
Version 1 has full software on Digiland website.
http://www.digi-land.net/Photo_Show.asp?InfoId=487&ClassId=56&Topid=53
If you have version one you should be able to use software as is, if you have version 2, like I do you will need to edit build.prop else touch screen will be wrong, plus screen will be upside down.
You can flash full software if you want, I only flash system.
this is my method to flash system, once you have downloaded the software unpack it, need to have custom recovery, boot tablet into custom recovery.
Code:
adb reboot recovery
unmount cache
mount system
mount data
mount cache
rm -rf /system/*
rm -rf /data/*
rm -rf /cache/*
adb reboot bootloader
fastboot flash system system.img
power off tablet, or press reset button in back
hold power up + volume up to get into boot selection
choose recovery then tab volume down.
when recovery fully loads.
unmount cache
mount system
mount data
mount cache
adb pull /system/build.prop
change ro.sf.hwrotation=90 to ro.sf.hwrotation=0
adb push build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
reboot
You should now be able to use the software, somethings may be a little off camera and so on but non the less software is usable.
Don't like software use recovery to restore your back up.
Click to expand...
Click to collapse
Digiland has made the update files,etc available on their website http://www.digi-land.net/upload/DL701Qupdate_software.rar
There are no instructions on the site. Maybe someone can help a noob reflash/update with these files? I have a rooted device, but can't do the wireless update because it says system was damaged and update is disabled. I would like to update and re-root.
SYN1ST3R said:
Digiland has made the update files,etc available on their website http://www.digi-land.net/upload/DL701Qupdate_software.rar
There are no instructions on the site. Maybe someone can help a noob reflash/update with these files? I have a rooted device, but can't do the wireless update because it says system was damaged and update is disabled. I would like to update and re-root.
Click to expand...
Click to collapse
If you can't follow the instructions included with the update, Then you need to contact Digiland.
This thread isn't about teaching newbies to install updates. You can start your own thread, How to install updates for Digiland tablets if you want.
sent from my kingSing T1 via taptalk
vampirefo said:
If you can't follow the instructions included with the update, Then you need to contact Digiland.
This thread isn't about teaching newbies to install updates. You can start your own thread, How to install updates for Digiland tablets if you want.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
A bit hard to follow instructions that DON'T exist
vampirefo said:
fastboot flash recovery DL701Q_dual_boot_recovery.img
Click to expand...
Click to collapse
I'm flashing this file, but I'm still ending up in the stock recovery, not CWM. Has anyone else had this issue?
Code:
> adb reboot bootloader
> fastboot flash recovery DL701Q_dual_boot_recovery.img
sending 'recovery' (6248 KB)...
OKAY [ 0.155s]
writing 'recovery'...
OKAY [ 0.888s]
finished. total time: 1.044s
freakified said:
I'm flashing this file, but I'm still ending up in the stock recovery, not CWM. Has anyone else had this issue?
Code:
> adb reboot bootloader
> fastboot flash recovery DL701Q_dual_boot_recovery.img
sending 'recovery' (6248 KB)...
OKAY [ 0.155s]
writing 'recovery'...
OKAY [ 0.888s]
finished. total time: 1.044s
Click to expand...
Click to collapse
No ideal why it doesn't work for you, you could try the splashtool.
Sent from my Venue 8 3830 using Tapatalk
freakified said:
I'm flashing this file, but I'm still ending up in the stock recovery, not CWM. Has anyone else had this issue?
Code:
> adb reboot bootloader
> fastboot flash recovery DL701Q_dual_boot_recovery.img
sending 'recovery' (6248 KB)...
OKAY [ 0.155s]
writing 'recovery'...
OKAY [ 0.888s]
finished. total time: 1.044s
Click to expand...
Click to collapse
I'm having a similar issue. Tried this way and the TWRP guide. Ever attempt says successful but ends up frozen on the normal boot splash screen when trying to manually or adb into recovery.
Could be your device is different, you made need to use your own kernel.
Unpack your boot.img, then unpack my recovery and swap out kernels then repack and flash.
Sent from my BLU STUDIO 5.0 C using Tapatalk
Hello. Just bought 2 of these tablets from Best Buy today. It would seem I have all the correct drivers installed, both adb and fastboot see my device but even though I have the custom recovery .img on both my micro sd card and the tablets internal storage when i type the command "fastboot flash recovery DL701Q_dual_boot_recovery.img" I get back the error "error: cannot load 'DL701Q_dual_boot_recovery.img'. What am I doing wrong? Where does the file have to be for fastboot to find it?
EDIT: Nevermind. Been awhile since I've tinkered with flashing a tablet. For others that might not know the file to be flashed needs to be in the same folder as the fastboot.exe.
Okay installing the custom recovery went great but I've tried numerous times to install the root zip file from recovery and haven't gotten root even after about 5 tries. I think I read somewhere that this method was somehow blocked in newer firmware. Perhaps I have that firmware. Kernel version on my "About Tablet" says "3.4.67 [email protected] #1 Fri Apr 3 15:55:00 CST 2015" and "Build number is " ALPS.KK1.MP10.V1.45" if that means anything to anyone.
Tried some iRoot crap which is probably exactly what it is and didn't end up with anything but a bunch of chinese bloatware on my tablet, which I promptly deleted, but no root.
Would flashing one of the older firmware definitely get me root?
InfernoShark said:
Okay installing the custom recovery went great but I've tried numerous times to install the root zip file from recovery and haven't gotten root even after about 5 tries. I think I read somewhere that this method was somehow blocked in newer firmware. Perhaps I have that firmware. Kernel version on my "About Tablet" says "3.4.67 [email protected] #1 Fri Apr 3 15:55:00 CST 2015" and "Build number is " ALPS.KK1.MP10.V1.45" if that means anything to anyone.
Tried some iRoot crap which is probably exactly what it is and didn't end up with anything but a bunch of chinese bloatware on my tablet, which I promptly deleted, but no root.
Would flashing one of the older firmware definitely get me root?
Click to expand...
Click to collapse
You have to follow OP exactly, what is happening is you are just trying to flash a zip without doing the mounts and umounts in OP.
Unmount cache
Mount system
Mount data
Mount cache
Now flash root zip.
Sent from my NXA8QC116 using Tapatalk
vampirefo said:
You have to follow OP exactly, what is happening is you are just trying to flash a zip without doing the mounts and umounts in OP.
Unmount cache
Mount system
Mount data
Mount cache
Now flash root zip.
Sent from my NXA8QC116 using Tapatalk
Click to expand...
Click to collapse
I love you man! LOL! Root is a go, verified by Root Checker! :good: