Unable to update rk3118 android box - Android Q&A, Help & Troubleshooting

Hi im attempting to flash my box with the latest RK3118 Q7 firmware, im currently using a 2013 build.
I am unable to flash it using the RKbatch tool as even though the drivers are installed the tool will not pick up my box as connected. (Abd command shows my device as connected with no issues)
Device manager shows the device as rk31sdk under USB devices after installing drivers (device is in recovery mode) However Batch tool will still not see my device
Therefore I have attempted to flash using the recovery menu and zipping my .img file.
Below are the steps I follow:
Loaded a fat32 formatted with my zipped img file (no other files on card)
wipe data/factory reset>update image from external storage
I then choose my zipped img file and the screen shows verifying update package, but then shows installation aborted. (Tried 2 separate zipped images)
I can boot from the backup fine, however I need the 2015 image as my build was so old i was no longer able to download from the play store.

Related

[Q] <waiting for device> on P500

Ok so I was trying to install a custom recovery on my P500 and when it turned on it gave me this message
fast boot mode started
udc_start
Click to expand...
Click to collapse
I plug it in it gives me
fast boot mode started
--suspend--
--reset--
--port/change--
--reset--
--port/change--
Click to expand...
Click to collapse
I tried out this method: http://forum.xda-developers.com/showthread.php?t=1088046
After keying the fastboot commands in it says <waiting for device>. Some Google hits told me that it's because I don't have latest USB drivers. I'm sure I do, but I've re-installed them just to be sure. But to no avail.
I'm still on my stock ROM (untouched), phone is rooted (duh) and this is my first attempt to install a custom recovery.
Not allowed to post on that thread ofc, my first post here. All help greatly appreciated. Thanks
Here is the Simple way ..try it
this link for latest working Rom >>
http://forum.xda-developers.com/showthread.php?t=946354
how to root >>
Enable USB debugging on your phone by going to Settings –> Applications –> Development. Check the ‘USB Debugging’ option.
Make sure you have a SD card inserted and mounted in your phone (Don’t know if it’s necessary but before proceeding further I formatted my SD card after taking a backup of the data in it. Why take a risk? Smile)
Download the GingerBreak APK from XDA Developers and get it onto your phone.
Install it by browsing to the GingerBreak APK in any file manager.
Open GingerBreak from your app drawer and press the root button.
Wait for a few minutes. If there are no problems, the device will reboot itself. (The reboot will take quite some time.)
You will see a SuperUser app in your app drawer after the reboot. Open it and see if it is working.
You now have a rooted Optimus One P500 phone.
Now install custom recovery
Follow the below steps to install custom recovery on your LG Optimus One P500.
Install Android Terminal Emulator from Android Market.
Download the file "amon_ra_recovery_installer.zip" from here or here.
Check the MD5 hash value of the downloaded ‘zip’ file. You can use HashTab to do this. Right click on the downloaded file and ensure the MD5 matches 86db8a52b01f049cadb8f097a4c5bd9e.
Extract the contents of the ‘zip’ file to the root of the SD card (Don’t extract inside any folder. For example if your SD Card is mounted on J: in Microsoft Windows then the four extracted files should be right under J:/ like J:/flash_image)
Open the terminal emulator app on your phone and type ‘su’ without the quotes. This will prompt a popup on your phone from the SuperUser app asking you whether you want to give root permissions for the terminal emulator app. Click ‘Allow’ and proceed. The shell prompt will change from the previous user shell ‘$’ to root shell ‘#’ in the emulator.
Now type in the following command and press Enter. The custom recovery will be flashed on to your phone and it will reboot into Custom Recovery.
sh /sdcard/rf.sh
Shut down your phone and boot into Recovery using the Volume Down, Home and Power switch keys. You can move through the options using the volume up/down keys. Use the Menu button to select the option.
In the recovery menu, select Backup/Restore, then select Nand backup. What this will do is backup your current ROM on your SD card, if something goes wrong while flashing the new ROM you can simply boot into recovery and restore your previous ROM.
Connect the phone to your computer and inside Recovery main menu click the option ‘USB-MS toggle’ and then ‘USB-MS Toggle SDCard’. This will unmount the SD card so that you can see it in your computer. Backup everything from your SD Card. Eject from computer and toggle USB again from recovery to mount the SD card back in phone.
Though it is not a necessity for this ROM, I would suggest partitioning your SD card to create swap and ext partitions. The ext partition will come in use if you want to install apps onto your SD card later. This is different from what you see in Froyo versions of Move to SD option. Partitioning will format your SD card, so make sure you backup your SD card as mentioned in Step 3.
Go back to the recovery menu again and select ‘Partition sdcard’. Then select ‘Partition SD’. Create a swap partition of size 0 and ext partition of size 512. Once done hit Back to go again to the ‘Partition sdcard’ menu. Convert the partition you just created to ext 3 and then ext4 using the options ‘SD:ext2 to ext3’ and ‘SD:ext3 to ext4’.
Toggle USB from recovery again. Inside the SDcard create a folder AAA and copy the ROM you downloaded in Step 1 into the folder ‘AAA’ on your SDCard. Once done, eject the SD card and toggle USB again to mount the SD Card in the phone again.
Go to the Wipe option in the recovery menu and wipe userdata, /data, /sd-ext, /sdcard/.android_secure, /cache, ‘Dalvik-cache’
Then go to the Flash Zip option in the recovery menu and select the zip file you copied in Step 6.
Sit back and relax while the zip is flashed. Once recovery shows that flashing is complete, reboot phone from recovery. The first boot will take quite some time.
Enjoy Gingerbread 2.3 on your LG Optimus One P500.
@ above completely unrelated to his problem.
Sent from my LG Optimus One P500 using XDA App
Appreciate your post but it has nothing to do with query sadly.
I was doing what you've mentioned in the installing recovery section when things went wrong.
I run Win7 x64 btw.
istoner said:
Some Google hits told me that it's because I don't have latest USB drivers. I'm sure I do, but I've re-installed them just to be sure. But to no avail.
Click to expand...
Click to collapse
That is correct - drivers issue.
1/ Add DEVMGR_SHOW_NONPRESENT_DEVICES to your environment on Windows and set the value to 1. (In Advanced system settings, Google if you do not know how.) Log off and log back on.
2/ Run devmgmt.msc
3/ There, View - Show hidden devices
4/ Go thru it and uninstall everything Android-related (for starters, ADB Interface and stuff under it, Disk drives, Modems, Ports (COM and LPT), USB controllers - might not be complete list above)
5/ Reboot the PC.
6/ Install the latest drivers for your phone.
7/ If it worked, once you have plugged in the phone stuck in fastboot mode, in device manager you should see Fastboot interface (Google USB ID) in ADB Interface section.
Thanks, trying that out now.
doktornator,
Thanks a bunch. It was an issue with the drivers, I tried your method a few times with little success. Then I let Windows find the drivers (out of all the things), and that worked. Relieved and slightly embarrassed that Windows could what I couldn't
Good that it works now. Fingers crossed to unbrick your phone soon.
Oh it's unbricked and ready to go again lol.
Hi, I am on Windows XP with the exact same problem.
Have tried the B2CApp for driver updates with no luck. Tried windows automatic driver installation,again no luck.
Anything else that I could try on a Win XP machine?
UPDATE:
I have fixed the issue. Got the drivers mentioned in this thread:
Anyone else stuck with Windows XP not recognizing the device even after the B2CApp installation, try these drivers:
http://android.modaco.com/topic/324744-waiting-for-devicefastboot/#
hi guys
Same issue here...and I've had all of the above problems (missing dll, the "waiting for device" due to the absence of proper drivers, etc) . I was able to solve everything up to step 2 of the procedure, i.e., when I type "fastboot flash recovery recovery.img" I get the error message: "cannot load recovery.img".
I tried with both the .img files extracted from the CWM link and AmonRA (thinderg). Any ideas? What am I doing wrong? This is going for hours now and I'm getting desperate!
droidao said:
hi guys
Same issue here...and I've had all of the above problems (missing dll, the "waiting for device" due to the absence of proper drivers, etc) . I was able to solve everything up to step 2 of the procedure, i.e., when I type "fastboot flash recovery recovery.img" I get the error message: "cannot load recovery.img".
I tried with both the .img files extracted from the CWM link and AmonRA (thinderg). Any ideas? What am I doing wrong? This is going for hours now and I'm getting desperate!
Click to expand...
Click to collapse
is the name of the .img file recovery.img?
the command is really fastboot flash recovery (name of file).img
Yes it is...Actually I tried both ways (renaming and keeping the original name)! But I've finally figured it out!!! Here was the problem: when I installed android sdk I added the paths of the required directories (tools and platform-tools) to the system variable section so I could launch tools without writing the path all the time...However, because desperate times call for desperate (and often silly) measures, I decided to type the command cd "name-of-directory" anyway and that...made the trick.
This community is indeed great...I'm going to distribute some "thankyous" now!
I had the same problem with Win7, Updating the drivers from the device manager of w7 worked for me. Hope it helps.
Ps: will take around 15 mins updating.

Stock to CM9 - A complete guide

I couldn't find a guide for the complete process in these forums, so I thought I'd write my own. I used this exact process for a US player, 5.0 (YP-G70). I don't know what's different for the international or 4.0 versions. As Quinman22 mentions international users should use Rumirand's CWM kernel instead of Entropy's.
Also, if you see any errors, or omissions, please, please, please let me know so I can fix them. I'd like this guide to be as accurate, complete, and generally useful as possible.
First of all, download all the necessary files:
(downloads marked with a * need to be extracted into the same folder, with no subfolders)
Heimdall http://www.glassechidna.com.au/products/heimdall/
Zadig libusb drivers http://sourceforge.net/projects/libwdi/files/zadig/zadig_v2.0.1.154.7z/download
Entropy's Clockwork Image http://forum.xda-developers.com/showthread.php?t=1445840 (be sure to decompress/extract the file after you download it)
CyanogenMod 9 http://www.mediafire.com/?1blgg21e3f0pyk4 (do NOT extract/decompress)
(optional) Google Apps (needed for app store, gmail, voice search, etc.) http://goo.im/gapps/gapps-ics-20120429-signed.zip
Kies http://www.samsung.com/us/kies/
OR
GB-Stock-Safe-v5.zip (bunch of flashing tools and files in one handy download) http://hotfile.com/dl/146572150/5fb9a3c/
Prepare your PC
Download and Install Heimdall
(http://www.glassechidna.com.au/products/heimdall/)
Install Samsung's Drivers.
Install Samsung's Drivers (from Kies, or SAMSUNG_USB_Driver_for_Mobile_Phones.msi either from Kies or SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe from GB-Stock-Safe-v5.zip)
You should reboot your computer after installing, even if it doesn't tell you to. Drivers may not initialize if you don't.
Initialize the drivers for the other two modes:
Power off your device then boot it into download mode by holding the VOL- button while you power it on.
Power off your device then boot it into recovery mode by holding the VOL+ button while you power it on
Install and configure zadig libusb
Reboot your device into Download mode as previously described
Run zadig.exe
Go to Options > List All Devices
Select Samsung USB Composite Device from the dropdown box
Click Install Driver (accept any unsigned driver prompts you get)
Once Zadig says the drivers are installed successfully, close it
Congratulations, your PC is ready.
Prepare your device:
Copy the CM9 and GAPPS files to your device (the complete .zip files)
Flash the Device
Install Entropy's ClockwordMod on your device
1.1 Connect device to your PC (using the same physical usb port you used to configure zadig libusb)
reboot your device into download mode (hold down VOL- & pwr)
from a command line, type "heimdall flash --kernel zImage --verbose" (no qutoes)
Let heimdall do it's thing
Reboot your device after that's finished
Backup your current system
Boot into recovery mode (VOL+ & pwr)
use VOL+ and VOL- keys to highlight 'backup and restore' then press pwr to select it
Choose whichever backup location you prefer (default is external sd card)
(optional) if you want to copy this backup over to your pc now, you can go to 'Mounts and Storage' > 'mount USB Storage' to access the file system from your PC
Select Go Back until you're back at the main recovery menu
Start with a clean slate
In recovery mode use the 'wipe data/factory reset' option (This just wipes user, app, and some system data)
Go to Advanced -> Wipe Dalvik Cache (This where droid stores the compiled files for installed apps. Leaving old data here can cause you serious headaches later on)
Flash CM9
From the main recovery menu, select 'install zip from sdcard' (or '... from internal sdcard' if you saved it to the external sdcard)
ALL DATA will be lost after you select yes (that's why we made a backup earlier)
Let the device do it's thing
Reboot into recovery mode (make sure USB cable is disconnected before you power off the device, CM9 gets stuck in a boot loop if it's powered off while charging)
Select install zip from sdcard
Again, select the appropriate 'choose zip ...' option
select the gapps file you copied over earlier and select yes (note: this does NOT overwrite system settings and data, so don't worry)
Let the device do it's thing
select reboot system from recovery menu
You're done
You've now got CyanogenMod 9 installed on your player, along with the google apps package (email, app store, search, etc.). Now you get to configure the system settings as you like, and reinstall all your apps.
If you want to restore an apps settings, or saved games, that'll be in another thread.
(Edited per Quinman's suggestion)
I may have missed it, but I hope you mentioned that this method is for US devices. INTL users would flash Rumirand's kernel instead of Entropy's.

Please help me !!

I rooted my device which is a huawei p8 max with the kingroot apk and i installed the twrp recovery (the MATE S TWRP) which still works.
Unfortunately i deleted EVERYTHING in my p8 max.. there are NO DATA and NO SYSTEM files.
There's only the mate s recovery that works.
I tried to flash a zip with the stock firmware inside but the recovery showed me "unable to mount '\system' " and "Zip file is corrupt!" in red.
In addiction, my pc can't even recognize my p8 max, but it shows a connected device called "CRR - L09" that is my phone.
It is shown as an MTP device because I DIDN'T ENABLE THE USB DEBUGGING on my phone.
Is has a folder "internal storage" in which i put my zip with the stock firmware to flash(i said it didn't work) and other 2 sub-folders that are "TWRP" and "obb". Just these two.
My HiSuite(the huawei tool) can't recognize of course my device
__________________________________________________ ___
bootloader unlocked
twrp installed and working
root
my pc sees just an mtp device (CRR - L09)
device EMPTY with just an internal storage with other 2 folders (twrp,obb)
__________________________________________________ ___
I'M SO FRUSTRATED, IF IT'S POSSIBLE I'D LIKE TO HAVE MY PHONE BACK PLEASE

Recover Oneplus One device without system partition

I have tried to revert back my Oneplus from Nougat based ROM and custom kernel to the last Oxygen OS. I am using TWRP 3.1.1-0. I have downloaded and transferred the zip file containing Oxygen OS to the Downloads section and I have wiped, the cache and the system partition without making a backup and when I have tried to install the Oxygen OS it reports that: "Updater process ended with ERROR:7. Error installing zip file" . I have connected the phone to an USB cable but it doesn't appear as an external drive in My Computer so I am unable to transfer some old backup I have on my PC. I have tried to boot into bootloader and execute adb devices, but it is not recognized there as well. As a matter of fact when I have booted into the bootloader my PC installed some drivers and now the phone appears in Devices and Printers and is listed as Android as Unspecified category, but not present again under My Computer. Is this normal? What can I do to recover my device? How can I transfer some files between my PC and the phone?

Disassembling MBN Files

I am working on trying to root my Alcatel A50 (nice little phone I picked up on the cheap). In order to install SuperSU to get root access, I need to install a bootloader. By the looks of it, I should be able to make a working bootloader if I have the boot.img file. In order to extract boot.img from the phone, I need root access... a bit of a catch22...
I have so far managed to unlock the bootloader and download an official MBN file via the official Alcatel Windows updater. If I can figure out how to extract boot.img from this MBN file, then I may be able to get around the above3 catch 22.
From this MBN file (3.4 GB in size), I have managed to extract a bunch of apps (see my journal in the hidden section below for details of how I did that). However, part way through the extractor chokes and quits. Based on the size differential of what I am able to extract vs the overall size of the MBN file, I am sure that there is more lurking inside of this file beyond what was extracted - such as the desired boot.img.
What I have gleaned so far in my reading suggests that these MBN files are, in fact, a sort of executable binary file. To that end, I am wondering if anybody has had any luck disassembling these files/fully extracting their contents.
In case it helps (either for my query or some future endeavor in a related vein), here is what I have documented of my quest thus far (follow the directions/links/downloads at your own risk):
https://web.archive.org/web/2017070...bile.com:80/global-en/support/smartsuite/list
Enable OEM Unlock: http://techbeasts.com/how-to-enable-oem-unlock-on-android-nougat/
Install ADB and Fastboot. Go here: https://developer.android.com/studio/releases/platform-tools scroll down to the Downloads section and click on “SDK Platform-Tools for Windows” - it should be a 4-5 MB download. Unzip the files and navigate to the folder via CMD.exe.
As Alcatel seems to have merged with another company, it would appear that links to useful software, drivers etc have all been broken in the midst of their overhaul. I must say I was unimpressed with the limited information/downloads available from their present sites (even checking many of their international sites). At any rate, I managed to find a link to the Alcatel Smart Suite (https://web.archive.org/web/2017070...bile.com:80/global-en/support/smartsuite/list) via Archive.org. I simply selected the newest one and – behold – it downloaded.
Download Smart Suite → Install and load application. Plug in phone to install Alcatel ADB Driver. Reboot Windows
I did run into an issue when running “adb devices” after launching the Smart Suite where it was saying:
adb server version (31) doesn't match this client (40); killing...
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon
I found someone else had a similar issue (https://stackoverflow.com/questions...rsion-31-doesnt-match-this-client-36#38447003). As per the link, I closed Smart Suite and ran the following terminal commands:
adb kill-server
adb start-server
And that seemed to resolve the issue.
You will want to reboot the phone into fastboot mode with this command:
adb reboot bootloader
And verify that you have connectivity by running:
fastboot devices
Then type in this command:
fastboot oem unlock
Your phone will display some text prompting you to unlock the bootloader. Mine says:
Unlock bootloader?
If you unlock the bootloader, you will be able to install custom operating system software on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data from our phone (a “factory data reset”).
Press the UP/Down buttons to select Yes or No.
Yes: (Volume Up): Unlock (may void warranty)
No: (Volume Down): Do not unlock bootloader.
To continue, Press the Volume Up button on the phone.
Another site suggested I also run: fastboot flashing unlock. I am not sure if that is necessary, but I ran it for good measure. The procedure is the same as above.
Once it finishes, press and hold the power button to power the phone off. Then power it back up. Once it is finished erasing, set up the phone again, enable developer mode and USB debugging.
Next, we will need to obtain root access. To do this, we will install SUPERSU. Unfortunately, at the time of this writing, the official website only gives us XML files when trying to download the files. I did track down an unofficial mirror, though am not 100% sure of its veracity. Download the latest version (the zip file) and use ADB to push it to the phone (adb push filename.zip /sdcard/) and then use the onboard file manager to move it to your external SD card. Then reboot into recovery mode (adb reboot recovery).
Getting Original Firmware
http://www.alcatel-mobile.com/cari/support/softwareUpgrade/list
Download Mobile_Upgrade_S_Gotu2_v5.2.1_Setup.exe
• Install
• Shutdown Phone
• Load software & select 5085O
• Plug in Phone to initiate the downloaded
• (?Unplug phone) and wait for download to complete
• Go into C:\Mobile Upgrade S Gotu2 v5.2.1\download and grab the big file.
Extract Zip → Get MBM File
Either using CYGWIN or running it on Linux directly, execute the following perl script (as per this thread discussion - https://forum.xda-developers.com/an...p-4s-help-rooting-installing-t3514186/page9):
cat system.mbn | perl -pe 's/(\xFF{5}\x00{4}\xFF{54})[^\xFF]{10}(\xFF{16})/\1\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\2
/g' | perl -pe 's/(\xFF{32})\xA8\xCF\x56\xCF\xFA\x43\x09\x9F\x79(\xFF{32})/\1\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\2/g' > system.img
On Linux, install simg2img. Use this utility to convert the system.img to system.img.raw (cannot recall where I saw this tidbit)
Mount system.img.raw (mount system.img.raw /mnt/tmp)
sudo cp -R * /home/Downloads/temp/

Categories

Resources