Database Info

[GUIDE] Rooting and CWM on PORTRONICS LIMEBOX!!!!

For all you Indian Users, or anybody who owns a Portronics Limebox running GB; root and CWM has finally been achieved!
Disclaimer: I am not responsible if you end up bricking your device. This procedure has been known to work for my Limebox. Deviate from the procedure and you have no right to blame me....
After lots of hours of extensive searching (with absolutely no help from portronics), I found an exact match to our device: G-Box (See the Remote???). Our Device is a Rockchip Processor, specifically RK2918. Rockchip processors are known to lock down the /system partition with a filesystem called cramfs. Don't worry, that can be solved too!
Before we start, Understand the 3 modes you can set the device in:
1. Normal Power On (Self-Explanatory)
2. Recovery Mode (Stick a Pin in the Reset Hole and keep the Power Button pressed at the same time)
3. Flash Mode:
i. Disconnect the AC Power.
ii. Connect a USB Male to Male Cable in the LOWER PORT. (similar results don't come from the upper one). Connect the other end to the PC.
iii. Stick the Pin in the reset hole. Simultaneously, connect the AC Power.
iv. The device should turn on with a blue light and no display on the screen. The PC will detect the device. Use the flash mode drivers given below.
v. Flash Mode generally works in all conditions, even if it does not boot, unless you do something really stupid :fingers-crossed: !
Now onto the procedure!
Obtaining Root
1. As i mentioned earlier, our device is exactly similiar to 'G-Box'. See the thread here (on android forums) for all development pertaining to their device. Most of what I've mentioned here comes from this forum (Big thanks to all of them )
2. Download the Official Firmware here or a Modded Lite version here (credits to xzer0).
3. Download the img Unpacker (RK29xx ImageTools : big thanks to wendal!!)
4. Use the img Unpacker to unpack the Official/Modded Firmware. If you are downloading the Official, be sure to Pack the Firmware after unpacking, since it adds the root files to the image file then. You do not need to repack for the modded one, since that is pre-rooted.
5. The Firmware will be unpacked to a folder called 'Temp'. Ignore the folder 'System'.
6. Start the Flasher (RK29update.exe). Connect the device in Flash mode to your PC and install the drivers. RK29Update should detect the device (It will say 'Detected' or something like that at the bottom)
7. For Parameter, choose the parameter file inside the Temp folder. Do not touch the offset values AT ALL.
8. For Loader, choose the .bin file that has 'loader' in the file name (in the Temp folder). Let its offset be blank, if it is.
9. For all the remaining (except backup), point them to their respective files in the 'image' folder inside 'temp'.
10. Tick Mark all except Backup. Before Pressing Update, click Format. Let it finish and wait for the device to be re-detected.
11. Press Update and wait until it finishes and the device disconnects from your computer. (It may disconnect once or twice in between. Be patient. Look at the Log on the right side to be absolutely sure when to unplug it.)
12. Your device should immediately reboot into recovery. It will format /DATA, /CACHE and /uDisk. When it is done, it will reboot into Andoid. (Though the interface looks different, it is more or less an exact copy of the Portronics).
13. Enjoy your rooted Limebox!
Known Issues:
1. Moody at boot. Takes some time to show the 'ANDROID' text on the screen. Be patient.
2. Cant get into recovery on the modded firmware. The Recovery Mode trick causes it to simply switch off. No hassle, with Flash Mode, you have the best kind of recovery!
Optional Stuff (Be Careful. You have been warned. )
CWM Recovery
I technically do not encourage using CWM on this device because i've had bad experiences with it. But its nothing that can't be fixed with a re-flash. So.....the technique is simple. Obtain a recovery.img file (specifically for any RK2918 device) from here or here or anywhere you like. When you flash the new rom, in place of the recovery.img file in the \temp\image\ folder, choose this one. If additional files are given to flash, you can flash those too. However, like i said, there are complications, it may not always work. But if you face any issues, simply reflash with the official recovery.
Removing Apps
If you wish to remove apps from the Official or Modded firmware (which is difficult, since its locked down with cramfs), after unpacking the image, go into \system\app\, delete the apps you dont want and then repack (Important!). For some reason, I've never been able to add an app. You don't need to do it this way if you use the Ext3 Image (Read on!!!)
Ext3 FileSystem
So, as i mentioned earlier, you can get a system.img that is of ext3 filesystem instead of cramfs. Simply download the image file from here and use that for the same flashing procedure. (Credits to Finless (Bob) and Paincake)
Need someone for small testing!
Can somebody find the /backup folder in the root directory? What are the contents?

unable to detect limebox on my win7 64bit laptop
3. Flash Mode:
i. Disconnect the AC Power.
ii. Connect a USB Male to Male Cable in the LOWER PORT. (similar results don't come from the upper one). Connect the other end to the PC.
iii. Stick the Pin in the reset hole. Simultaneously, connect the AC Power.
iv. The device should turn on with a blue light and no display on the screen. The PC will detect the device. Use the flash mode drivers given below.
v. Flash Mode generally works in all conditions, even if it does not boot, unless you do something really stupid :fingers-crossed: !
Now onto the procedure!
Obtaining Root
1. As i mentioned earlier, our device is exactly similiar to 'G-Box'. See the thread here (on android forums) for all development pertaining to their device. Most of what I've mentioned here comes from this forum (Big thanks to all of them )
2. Download the Official Firmware here or a Modded Lite version here (credits to xzer0).
3. Download the img Unpacker (RK29xx ImageTools : big thanks to wendal!!)
4. Use the img Unpacker to unpack the Official/Modded Firmware. If you are downloading the Official, be sure to Pack the Firmware after unpacking, since it adds the root files to the image file then. You do not need to repack for the modded one, since that is pre-rooted.
5. The Firmware will be unpacked to a folder called 'Temp'. Ignore the folder 'System'.
6. Start the Flasher (RK29update.exe). Connect the device in Flash mode to your PC and install the drivers. RK29Update should detect the device (It will say 'Detected' or something like that at the bottom)
7. For Parameter, choose the parameter file inside the Temp folder. Do not touch the offset values AT ALL.
8. For Loader, choose the .bin file that has 'loader' in the file name (in the Temp folder). Let its offset be blank, if it is.
9. For all the remaining (except backup), point them to their respective files in the 'image' folder inside 'temp'.
10. Tick Mark all except Backup. Before Pressing Update, click Format. Let it finish and wait for the device to be re-detected.
11. Press Update and wait until it finishes and the device disconnects from your computer. (It may disconnect once or twice in between. Be patient. Look at the Log on the right side to be absolutely sure when to unplug it.)
12. Your device should immediately reboot into recovery. It will format /DATA, /CACHE and /uDisk. When it is done, it will reboot into Andoid. (Though the interface looks different, it is more or less an exact copy of the Portronics).
13. Enjoy your rooted Limebox!
Known Issues:
1. Moody at boot. Takes some time to show the 'ANDROID' text on the screen. Be patient.
2. Cant get into recovery on the modded firmware. The Recovery Mode trick causes it to simply switch off. No hassle, with Flash Mode, you have the best kind of recovery!
Optional Stuff (Be Careful. You have been warned. )
CWM Recovery
I technically do not encourage using CWM on this device because i've had bad experiences with it. But its nothing that can't be fixed with a re-flash. So.....the technique is simple. Obtain a recovery.img file (specifically for any RK2918 device) from here or here or anywhere you like. When you flash the new rom, in place of the recovery.img file in the \temp\image\ folder, choose this one. If additional files are given to flash, you can flash those too. However, like i said, there are complications, it may not always work. But if you face any issues, simply reflash with the official recovery.
Removing Apps
If you wish to remove apps from the Official or Modded firmware (which is difficult, since its locked down with cramfs), after unpacking the image, go into \system\app\, delete the apps you dont want and then repack (Important!). For some reason, I've never been able to add an app. You don't need to do it this way if you use the Ext3 Image (Read on!!!)
Ext3 FileSystem
So, as i mentioned earlier, you can get a system.img that is of ext3 filesystem instead of cramfs. Simply download the image file from here and use that for the same flashing procedure. (Credits to Finless (Bob) and Paincake)
Need someone for small testing!
Can somebody find the /backup folder in the root directory? What are the contents?[/QUOTE]

My apologies for the very late reply. As I recall, the drivers are for 32bit, have you repeated the steps on a 32bit machine? Did the pc attempt to recognize it?
huzefaid said:
3. Flash Mode:
i. Disconnect the AC Power.
ii. Connect a USB Male to Male Cable in the LOWER PORT. (similar results don't come from the upper one). Connect the other end to the PC.
iii. Stick the Pin in the reset hole. Simultaneously, connect the AC Power.
iv. The device should turn on with a blue light and no display on the screen. The PC will detect the device. Use the flash mode drivers given below.
v. Flash Mode generally works in all conditions, even if it does not boot, unless you do something really stupid :fingers-crossed: !
Now onto the procedure!
Obtaining Root
1. As i mentioned earlier, our device is exactly similiar to 'G-Box'. See the thread here (on android forums) for all development pertaining to their device. Most of what I've mentioned here comes from this forum (Big thanks to all of them )
2. Download the Official Firmware here or a Modded Lite version here (credits to xzer0).
3. Download the img Unpacker (RK29xx ImageTools : big thanks to wendal!!)
4. Use the img Unpacker to unpack the Official/Modded Firmware. If you are downloading the Official, be sure to Pack the Firmware after unpacking, since it adds the root files to the image file then. You do not need to repack for the modded one, since that is pre-rooted.
5. The Firmware will be unpacked to a folder called 'Temp'. Ignore the folder 'System'.
6. Start the Flasher (RK29update.exe). Connect the device in Flash mode to your PC and install the drivers. RK29Update should detect the device (It will say 'Detected' or something like that at the bottom)
7. For Parameter, choose the parameter file inside the Temp folder. Do not touch the offset values AT ALL.
8. For Loader, choose the .bin file that has 'loader' in the file name (in the Temp folder). Let its offset be blank, if it is.
9. For all the remaining (except backup), point them to their respective files in the 'image' folder inside 'temp'.
10. Tick Mark all except Backup. Before Pressing Update, click Format. Let it finish and wait for the device to be re-detected.
11. Press Update and wait until it finishes and the device disconnects from your computer. (It may disconnect once or twice in between. Be patient. Look at the Log on the right side to be absolutely sure when to unplug it.)
12. Your device should immediately reboot into recovery. It will format /DATA, /CACHE and /uDisk. When it is done, it will reboot into Andoid. (Though the interface looks different, it is more or less an exact copy of the Portronics).
13. Enjoy your rooted Limebox!
Known Issues:
1. Moody at boot. Takes some time to show the 'ANDROID' text on the screen. Be patient.
2. Cant get into recovery on the modded firmware. The Recovery Mode trick causes it to simply switch off. No hassle, with Flash Mode, you have the best kind of recovery!
Optional Stuff (Be Careful. You have been warned. )
CWM Recovery
I technically do not encourage using CWM on this device because i've had bad experiences with it. But its nothing that can't be fixed with a re-flash. So.....the technique is simple. Obtain a recovery.img file (specifically for any RK2918 device) from here or here or anywhere you like. When you flash the new rom, in place of the recovery.img file in the \temp\image\ folder, choose this one. If additional files are given to flash, you can flash those too. However, like i said, there are complications, it may not always work. But if you face any issues, simply reflash with the official recovery.
Removing Apps
If you wish to remove apps from the Official or Modded firmware (which is difficult, since its locked down with cramfs), after unpacking the image, go into \system\app\, delete the apps you dont want and then repack (Important!). For some reason, I've never been able to add an app. You don't need to do it this way if you use the Ext3 Image (Read on!!!)
Ext3 FileSystem
So, as i mentioned earlier, you can get a system.img that is of ext3 filesystem instead of cramfs. Simply download the image file from here and use that for the same flashing procedure. (Credits to Finless (Bob) and Paincake)
Need someone for small testing!
Can somebody find the /backup folder in the root directory? What are the contents?
Click to expand...
Click to collapse

tried on 32bit machine, the pc did'nt recognize it
please help
do i need to connect monitor with hdmi port to view flash mode.?
i have press reset pin and also powered on the device at same time, but my pc did'nt recognize it.i have also started rk29androidtool to check it it detects the device but no luck.

[ASUS PADFONE 2] [How to] Change SKU. Switch from WWE to CHT,TW, etc.. and vice versa

Introduction.
Sorry for my English, if I wrote something incorrectly, correct me!
Make sure you have installed the Asus's driver. If you have no idea or do not know how, ask.
I used ADB Android SDK ( h-t-t-p://developer.android.com/sdk/index.html , it is located in sdk\platform-tools), make sure ADB recognizes the PF2 before.
The command you type in the terminal:
adb devices
I have run ADB from Windows, but if you use Ubuntu (or Linux in general) basically the syntax is the same.
If you have never sent a file via ADB in recovery, give it a try with any file before proceeding with the guide, so you know what you're doing when you get to step 4 and, above all, if you fail you will not formatted PF2 in vain.
The command you type in the terminal:
adb push filename.extension /data/media
"adb" is the name of the exe file in the folder where you execute it, you can also write adb.exe is the same;
"push" is the command that sends the file;
"filename.extension" is the file you want to send (example update.zip). The file to be sent must be in the same folder as adb.
"/data/media" is the destination path where the file will be copied. In our case that is the internal memory of the PF2.
Obviously before starting any command you have to move to the folder containing the file adb.exe (sdk\platform-tools if you have downloaded the Google ADT)
The PF2 must have the original recovery.
I personally changed SKU from WWE to CHT and vice versa before writing this simple guide.
My PF2 had the bootloader unlocked when I made the change, it should work with the bootloader locked, but my advice is to unlock it before you play because if something goes wrong, there is a chance to do something through fastboot for revive him.
Here we go:
1. Copy to the phone's internal memory the firmware you want to install, then reboot into recovery.
2. Select "apply update from external storage" and choose the zip file to flash.
At this point the recovery changes the partition table and then restarts.
On reboot we will have a nice "Installation aborted", this because, being changed the partition table, the recovery can not find the file to flash as it the partition containing the data has been reformed losing its contents. So you will need to copy the file again via adb.
3. Select "wipe data / factory reset"
You need to do a wipe, because it formats the partition where we will send the file. Having just changed, the partition has not a file system and so it must be formatted to save something on it.
4. Send via adb the firmware:
adb push xxxx.zip /data/media
5. Wait until the firmware is sent to PF2. ADB has spent 148 seconds to send the WWE (~ 713 Mb) and 172 seconds to send the CHT (~ 813 Mb).
You will not see any progress bar, so do not panic and just wait for the terminal will show the message sending done.
6. Select "apply update from external storage" and choose the zip file to flash.
The recovery will restart again, but this time the partition will not be changed so it will proceed with the upgrade.
Finished updating the PF2 restarts.
I suggest you do a wipe after the update in order to have a clean installation.
It 'important to note that when you make a change from one SKU (WWE, TW, CHT etc ...) to another one, it goes beyond the point 2 only if the recovery changes the partition table.
If you have any doubt, ask, I'll be happy to update some step in more detail.
I hope you enjoy it.
gsep

I'll link this to the thread so others will have an easy time to find this

walaway said:
I'll link this to the thread so others will have an easy time to find this
Click to expand...
Click to collapse
Thanks
hope in our subsection in future.

gsep said:
My PF2 had the bootloader unlocked when I made the change, it should work with the bootloader locked, but my advice is to unlock it before you play because if something goes wrong, there is a chance to do something through fastboot for revive him.
Click to expand...
Click to collapse
Hi...thanks very much for the tips and very detailed instruction.....but, have u tried the steps without unlocking the bootloader? and if i want to go back tot he original SKU, i just need to replace the firmware.zip with the correct one from Asus web and repeat the whole thing? Just in case for warranty purposes....
Thanks again!!!

pgkia said:
Hi...thanks very much for the tips and very detailed instruction.....but, have u tried the steps without unlocking the bootloader? and if i want to go back tot he original SKU, i just need to replace the firmware.zip with the correct one from Asus web and repeat the whole thing? Just in case for warranty purposes....
Thanks again!!!
Click to expand...
Click to collapse
I only have tried with unlocked PF2.
For go back you have to follow always this guide.

gsep said:
Introduction.
Here we go:
1. Copy to the phone's internal memory the firmware you want to install, then reboot into recovery.
2. Select "apply update from external storage" and choose the zip file to flash.
At this point the recovery changes the partition table and then restarts.
On reboot we will have a nice "Installation aborted", this because, being changed the partition table, the recovery can not find the file to flash as it the partition containing the data has been reformed losing its contents. So you will need to copy the file again via adb.
3. Select "wipe data / factory reset"
You need to do a wipe, because it formats the partition where we will send the file. Having just changed, the partition has not a file system and so it must be formatted to save something on it.
4. Send via adb the firmware:
adb push xxxx.zip /data/media
5. Wait until the firmware is sent to PF2. ADB has spent 148 seconds to send the WWE (~ 713 Mb) and 172 seconds to send the CHT (~ 813 Mb).
You will not see any progress bar, so do not panic and just wait for the terminal will show the message sending done.
6. Select "apply update from external storage" and choose the zip file to flash.
The recovery will restart again, but this time the partition will not be changed so it will proceed with the upgrade.
Finished updating the PF2 restarts.
I suggest you do a wipe after the update in order to have a clean installation.
It 'important to note that when you make a change from one SKU (WWE, TW, CHT etc ...) to another one, it goes beyond the point 2 only if the recovery changes the partition table.
If you have any doubt, ask, I'll be happy to update some step in more detail.
I hope you enjoy it.
gsep
Click to expand...
Click to collapse
i read some where on modaco, walaway mention this can be done with TWRP instead? Flash with TWRP in fewer steps. Is this true?

Did not work with me, not sure why?
First of all thanks for the detailed steps.
I have went through your steps more than 9 times before I decided to start with it.
I am on CHT (10.4.12.24-0)) and want to move to WWE (Latest) with unlocked bootloader.
Everything is alright until i reached step 2 where "At this point the recovery changes the partition table and then restarts."
The phone did not restart? it went straight to "Installation aborted" and nothing happened? Nothing was changed.
Not sure if the issue with the downloaded package? I got it from Asus official website "WWE_PadFone2_user_10_4_12_24_UpdateLauncher" but renamed it to "WWE" for easier adb command?
Any help will be appreciated
Edit: Downloaded file was supposed to be extracted from the .zip package, what a silly mistake it worked like charm. Thanks!

Why???
Why do I want to do this? If I go from CHT to WWE would it make my phone more compatible with tmobile?

Locked SIM
Hi all,
I did a Change from WWE to TW. The Thing is that my phone was not unlocked. After flashing to TW it worked a day and after that the SIM MODUL is totally blocked (IMEI = 0). I can not use any SIM Card.
I try to unlock the bootloader by means of the "Unlocker" app from ASUS, but it always says:
"An unknown error occurs, which may be a network connection issue. please wait and tray again later"
I tried to:
* Use the latest Version of WWE or TW Firmware
* Use an old Version of WWE Firmware
without success...
Does anyone have similar Problem ?

so this works because the system partition is blank?

[GUIDE] Videocon A55 HD Rooting and Recovery related stuff

Heya,
Since there is not enough info on the web regarding the rooting procedure for Videocon A55 HD and custom recovery for this awesomely smooth device, I'm uploading the necessary files and step by step guide. Hope it helps all the users of this device.
Remember rooting would tamper the warranty of the device and should be exercised carefully. The procedures mentioned below have been personally tested by me however I take no responsibility in case you ruin your device although I would be here to help you in such a scenario. Besides this the rooting script was not created by me and all the credit goes to the respective developer.
1. Rooting Procedure
Make sure you have enabled "USB Debugging" under Developer Options on your phone.
Keep your phone disconnected from computer via USB
a) Download and Install the ADB Interface driver for MTK 6589
Link to ADB Drivers
b) Download and extract the rooting package
Link to the Rooting Package
c) Now go to the extracted package and open a command prompt to that location as Administrator.
d) Type run.bat in Command Prompt and a message must appear "Press enter to root your phone..."
e) Press any key
f) Now after a few seconds the message should be " * daemon started successfully *"
g) Now connect your phone via USB to the computer
h) The cmd would automatically start pushing the necessary files onto your phone and when the process completes your phone will restart
Now you are rooted.To check install any Root checker application from playstore. Remember to grant permission while running Root Checker app when a pop up appears. It is suggested to update the SuperSU app from playstore and execute it at least once after that to update the su binary. You can also update the busybox package from playstore because busybox supplied with the rooting package is pretty old.
2. Installing CWM Recovery
Okie, since you are now rooted, most likely you would require a custom recovery to create full nandroid backups or test different ROMs. The CWM recovery provided here was created using MTKDroid Tools and is version 5.x (Non Touch). Again all credit goes to the developer of MTKDroid Tools for making such a powerful piece of software.
a) Download and extract the recovery package.
Link to CWM 5.x and Original Recovery for A55 HD
b) There are two files in the package , one is the custom CWM recovery and the other one is Stock Recovery (Names are pretty self understood)
c) Copy "Custom_Recovery_CWM_A55HD.img" to the root of your SD card
d) Rename it to "recovery.img"
e) Install Mobile Uncle Tools [MUT] from the playstore.
f) Open MUT and go to recovery update
g) Now you must see the recovery.img in a list. Just select it and follow the pop ups.
h) Now your phone would restart.
i) To check if the recovery update was successful, go to MUT and select "Reboot into Recovery" and your phone would most likely start in CWM recovery..
Alternative to get into recovery mode is to Press Power button + Volume Down key together when switched off.
3. Stock ROM for Videocon A55 HD
Okie, here we go, as I mentioned that I had got hold of the stock rom, so here I'm publishing it. The credit goes to Pratap Solunke (psolunke) for providing the Factory ROM zip.
I have just divided it into update.zip and files for SPFT for ease of downloading. Besides I have splitted each section into 4 parts and reuploaded it so you can download them at your ease. I'm providing the link for the whole folder which includes the changelog, update.zip and files for SPFT.
The ROM version is V7 (2013.07.15) which is different from the original ROM which was V5 (2013.06.08).
You can read the changelog for the updates in this ROM.
Link to ROM Folder
If using update.zip to flash this ROM, then
Step 1. Open the update.zip with winrar, Do not extract.
Step 2. Navigate to \META-INF\com\google\android\updater-script and extract this file only, then use "Notepad++" to open the file.Don't use default notepad.
Step 3. Delete assert(getprop("ro.product.device") == "A55HD" || getprop("ro.build.product") == "A55HD");
Step 4. Save the file, put it back to the same location in archive (It will take some time to add to archive)..Done...then proceed as usual.
a) update.zip is for reinstalling Factory Image of the ROM from recovery mode. The zip file is signed.
b) Files for SPFT are to be used with SP Flash Tool and can be used in case your phone is bricked. Do not flash the preloader unless you know what you are doing.
c) To download the files just go to the respective folder and right click on each file and hit download. After all four parts are downloaded, extract Part 1 of the downloaded splitted files and the files would be ready to be used as is.
d) Keep all four parts of the splitted files in a single folder and do not rename the splitted files.
If you have any questions related to A55 HD you can ask them here and I would try to help you the best way I can.
I'm still testing some custom ROMS but none seem to work . So far I've tested LEWA OS and MIUI ROM for xiacoao G6 Youth. However I'll keep trying and update once I have a working Custom ROM.
One more project in mind is to port Custom ROMS to A55 HD if none is available as is on the web.
If anyone of you is able to find a working Custom ROM for A55 HD kindly post it here so that we can have a repository of successful and useless attempts. I'm sure it would help others.

Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also.
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also. All the recoveries shown in the list are only remote recoveries

nanachitang420 said:
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also.
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Rooting procedure worked after two attempts. The device is rooted.
While trying to install CWM recovery, get a problem. Can not see custom recovery in MUT. Pasted on both SD cards, internal and external also. All the recoveries shown in the list are only remote recoveries
Click to expand...
Click to collapse
I forgot to mention , rename the recovery image to "recovery.img" and then put it in root of SD card and it would get detected by MUT...It will get detected instantly...Thankyou for bringing it to notice...Just updating the post...

done but some observations!!!!
DONE.
Some observations:
1. In CWM, cant see internal SD card. While, after mounting usb storage, can see external SD card only. NOTE, CANT SEE INTERNAL SD CARD ONLY WHEN TRY TO MOUNT INTERNAL PHONE STORAGE IN CWM. WHILE NORMAL WORKING NO PROBLEM.
2. Deleted.
3. Deleted.
4. Deleted,
5. Deleted.
6. The font size of Stock and CWM recovery is very small still it can serve the purpose.
Do any body have original/stock update.zip from Company?
Updates:
I think I figured out the problem with touch. Uninstalled an application called "Go Power Master" and the touch is ok even after connecting USB or charger. Thanks man. The phone is working very nice after rooting.

nanachitang420 said:
DONE.
Some observations:
1. In CWM, cant see internal SD card. While, after mounting usb storage, can see external SD card only.
2. After rooting, before even installing CWM, got some irratic behavior with touch. Like, while USB is connected, touch was not working as expected, it took long time to make USB storage active as after touching a specific required operation, like pulling down task bar it was doing something else like opening play store, opening game, or opening date and time settings. While unlocking lock screen, it was just opening any random phone application and is not even allowing to go back with back button or home button. Don't know this is related with what?
3. Irratic application were opening while touching different application but after removing USB, things were working better.
4. Rebooted in CWM and first tried to "fix permissions" to avoid that irratic touch behavior, thinking there was problem with permissions. Took nandroid back up, after fixing permissions. Wiped cache and dalvik cache and restarted.
5. Now, till now phone is not connected to PC with USB cable or connected to charging; it behaves better with touch but it is very troublesome to perform any operation after phone connected to PC with USB or to charger.
May be you have faced these issues or may not! Any suggested solution? Do any body have original/stock update.zip from Videocon?
Updates:
I think I figured out the problem with touch. Uninstalled an application called "Go Power Master" and the touch is ok even after connecting USB or charger. Thanks man.
Click to expand...
Click to collapse
For me the touch works without any problems...and as for detecting internal sd card...that also works flawlessly..i don't have the phone with me right now...Yesterday I was trying something and the nvram got corrupted [No baseband]...so right now it is resting at service center...Hope to get it next week...
One suggestion never install Carliv Touch Recovery on this phone...it messes with the baseband and display...Stick to this recovery until I build a more updated CWM...

Latest V-Store attached
Attached

nanachitang420 said:
Attached
Click to expand...
Click to collapse
Nice...let's make this thread a repository of A55 HD..And I have also got hold of the original update.zip and files for SPFT ...Will split them and upload to my google drive...and then share them..

update.zip
Aaaaanuj1 said:
Nice...let's make this thread a repository of A55 HD..And I have also got hold of the original update.zip and files for SPFT ...Will split them and upload to my google drive...and then share them..
Click to expand...
Click to collapse
The current version of my phone is 08062013. Can I flash this latest version through CWM and upgrade?

Tried to flash update.zip through CWM...
Installing: /sdcard/update.zip
Finding update package...
Opening update package....
Installing update....
assert failed: getprop("ro.product.device")=="A55HD" || getprop("ro.build.product")=="A55HD".
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Restored nandroid backup after this.

nanachitang420 said:
Installing: /sdcard/update.zip
Finding update package...
Opening update package....
Installing update....
assert failed: getprop("ro.product.device")=="A55HD" || getprop("ro.build.product")=="A55HD".
E: Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Restored nandroid backup after this.
Click to expand...
Click to collapse
Okie it is an easy fix...
Step 1.Open the update.zip with winrar, Do not extract.
Step 2.Navigate to \META-INF\com\google\android\updater-script ,use "Notepad++" to open the file.Don't use default notepad.
Step 3.delete assert(getprop("ro.product.device") == "A55HD" ||
getprop("ro.build.product") == "A55HD");
Step 4.Save the file, update to archive..Done

Done
Successful.
Please add in above step 2 "to extract file Updater-script on PC" and then use N.........
Flashed modified update.zip from CWM and phone upgraded to version 15072013. To be strange it is showing v1.0 20130715 in build ie in about phone. All the applications were intact but lost root and also CWM recovery; then managed to root the phone and flash CWM with your fantastic guide.
After booting in CWM, wiped cache and dalvik cache(why? don't know). Phone is working nice. Thanks,

nanachitang420 said:
Successful.
Please add in above step 2 "to extract file Updater-script on PC" and then use N.........
Flashed modified update.zip from CWM and phone upgraded to version 15072013. To be strange it is showing v1.0 20130715 in build ie in about phone. All the applications were intact but lost root and also CWM recovery; then managed to root the phone and flash CWM with your fantastic guide.
After booting in CWM, wiped cache and dalvik cache(why? don't know). Phone is working nice. Thanks,
Click to expand...
Click to collapse
Nice...Yeah, people at Videocon forgot to change the version number i guess...and loss of root and cwm was due to restoring of system.img and recovery.img in the ROM file...so it's normal..
Besides one should always perform a clean install from CWM..i.e. Clear Data, Clear Cache, Clear Dalvik Cache, Format /system/ and then install ROMS..
And yes this ROM is a bit better then the one on phone..I received my phone today from service center and software was updated to this ROM..It felt much better .And the version was same , so this seems to be the latest ROM for A55 HD.. Enjoy

How to flash phone with sp flash tools
was trying to flash a recovery build on CWM site. I think it has spoiled baseband. No sim is getting detected. Any idea how to flash phone with SP tool? Don't have access to service station as am very far.
Edit: Managed to flash with SP tool. Used the files you have uploaded for SPFT. Selected all options and now phone is on and showing base band version, also sim are getting detected. The issue was preloader drivers for windows 8 which managed to install by disabling driver signature verification. Device rooted and installation of CWM through MUT was successful. Thanks.
Try this and this. Its as good as custom rom installation works very well with MTK6589

nanachitang420 said:
was trying to flash a recovery build on CWM site. I think it has spoiled baseband. No sim is getting detected. Any idea how to flash phone with SP tool? Don't have access to service station as am very far.
Edit: Managed to flash with SP tool. Used the files you have uploaded for SPFT. Selected all options and now phone is on and showing base band version, also sim are getting detected. The issue was preloader drivers for windows 8 which managed to install by disabling driver signature verification. Device rooted and installation of CWM through MUT was successful. Thanks.
Try this and this. Its as good as custom rom installation works very well with MTK6589
Click to expand...
Click to collapse
You must understand that the recovery partition is of 6 mb....and most likely the recovery you received from CWM online builder was more than 6 mb..hence your secro.img was also overwritten...hence the problems with baseband and imei....same thing happened with me 7 days back when I had to submit my phone to Service center. Unfortunately i didn't had the flash image then but it is good to know that it can also recover baseband and imei. And congrats for recovering your phone and I'm glad my contribution helps you...
Just remember one thing...if the boot, recovery,secro partitions are of more than 6mb then don't flash them as they would mess one thing or other...and hopefully you had disabled preloader in SPFT.....if not then from next time onwards please do it....because rarely you need to flash preloader...and a wrong flash can make your device a brick which can only be recovered by Test points.Hence never flash preloader until unless you know what you are doing.....And yes, I already use Gravity Box along with Xposed Framework...Great mod...Besides them I also use xhalofloatingwindow with bubble launcher and lwinrecent ...Both are xposed modules and work as expected.I also have init.d support which allows to make boot persistent changes on device....Along with that a few build.prop tweaks that take my ROM to the custom level...Let me know if you need any of this...

Please
Thanks for preloader advise. was not that much aware and will take care next time. Please share init.d support, build.prop tweaks and their usefulness.

For init.d, use term-init by ryuinferno.
http://forum.xda-developers.com/showthread.php?t=1933849
This is the link to the thread. Do not use zip-init or uni-init. Follow the guide on the thread. It works flawlessly.
Sent from my A55HD using Tapatalk

Which other phones has MTK6589 and same config ?
Tell me model number and brand, i will try to upload stock firmware.
it will help us built custom rom with custom features.
@anuj - Anyways if it brick again and need to send service center, please text me imei and location, i will make it done fast for you dear.:fingers-crossed:

Thank you Pratap bro. I'll let you know next time if I get to the point where I need to go to service center but I'm sure that with the ROM you provided I wouldn't need to go to one. And yes people you can ask for stock ROM from Pratap. He has excellent connections and can get you at least the Videocon ROM and may be others . Don't forget to thank him. Besides he is an excellent person who wouldn't shy away from helping you if he can. Ciao Pratap brother.
Sent from my A55HD using Tapatalk

Any new updates from Videocon for our A55HD?

File not found
File not found bro

[GUIDE] Soft Bricked - Solution (Worked for me)

My Samsung Galaxy Note Pro 12.2 WiFi (SM-P900) got soft bricked after following a rooting tutorial i found by googling How to root SM-P900. I think the problem was that i used a too old (or wrong) version of Odin, but im not sure. While i was flashing the auto-root through Odin the screen turn of. After that it showed the "firmware upgrade encountered an issue. please select recovery mode in kies and try again" standard Samsung Message. I tried to reinstall the firmware through kies but with no luck.
[SOLUTION]
1. First I downloaded the correct firmware, from Sammobile. In my case it was Nordic Contries, cause i live in Denmark. Pick the one that suite you!!
2. Then i booted my first NotePro to download mode. It took my some tries, to get it working. First hold the power button. When the "Firmware Upgrade Encountered An Issue..." message turns off, in the same second, release the power button, and now select all three (Power + Volume Down + HomeKey). (You have to release the power button and press it again to make it work (At least for me)
3. Now install the stock firmware and your tablet is now working again.
4. (Optional) If you want to root your device and it didn't work the first time. Make sure you use the same Odin as showed in the tutorial.

invalid ext4 image
madsthines said:
My Samsung Galaxy Note Pro 12.2 WiFi (SM-P900) got soft bricked after following a rooting tutorial i found by googling How to root SM-P900. I think the problem was that i used a too old (or wrong) version of Odin, but im not sure. While i was flashing the auto-root through Odin the screen turn of. After that it showed the "firmware upgrade encountered an issue. please select recovery mode in kies and try again" standard Samsung Message. I tried to reinstall the firmware through kies but with no luck.
[SOLUTION]
1. First I downloaded the correct firmware, from Sammobile. In my case it was Nordic Contries, cause i live in Denmark. Pick the one that suite you!!
2. Then i booted my first NotePro to download mode. It took my some tries, to get it working. First hold the power button. When the "Firmware Upgrade Encountered An Issue..." message turns off, in the same second, release the power button, and now select all three (Power + Volume Down + HomeKey). (You have to release the power button and press it again to make it work (At least for me)
3. Now install the stock firmware and your tablet is now working again.
4. (Optional) If you want to root your device and it didn't work the first time. Make sure you use the same Odin as showed in the tutorial.
Click to expand...
Click to collapse
i AM FACING A PROBLEM HERE, PLEASE HEALP!
First I have download "P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar. md5" for my Galaxy Note Pro 12.2 SM-P905. But unfortunately the file did not work for me and after all the long installation process odin says failed. and the last line on my device is
"ODIN : Invalid ext4 image"
so, after seeing that I thought the downloaded file ("P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar.md5 ") may be corrupted. then I download again another file from sammobile website for my note pro SM-P905 and that is "P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar. md5" but when tried to install by odin after long time same condition happen again. Odin says failed, and my device last line was Invalid ext4 image.
what is the problem?
how to flash SM-P905?
where is the exact proper flash file for my SM-P905?
Please Healp!!!

ornobohornish said:
i AM FACING A PROBLEM HERE, PLEASE HEALP!
First I have download "P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar. md5" for my Galaxy Note Pro 12.2 SM-P905. But unfortunately the file did not work for me and after all the long installation process odin says failed. and the last line on my device is
"ODIN : Invalid ext4 image"
so, after seeing that I thought the downloaded file ("P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar.md5 ") may be corrupted. then I download again another file from sammobile website for my note pro SM-P905 and that is "P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar. md5" but when tried to install by odin after long time same condition happen again. Odin says failed, and my device last line was Invalid ext4 image.
what is the problem?
how to flash SM-P905?
where is the exact proper flash file for my SM-P905?
Please Healp!!!
Click to expand...
Click to collapse
1. You may want to try using:
http://samsung-updates.com/
instead of samfirmware, if you're experiencing corrupted downloads from the latter (but it's not very probable... see pt 3)
2. At the moment I am testing new firmware revision, downloaded from samsung-updates: P905XXUAND1 for NEE region. It flashed fine. Also, for most of the time I have used P905XXUANC3 firmware for DBT region (Germany - even if I am not a German, I do not really care about csc stuff, and I got used to the fact that the newest firmwares were always released for DBT region first on my old "standard" Note 10.1). It was flashing fine, too.
3. The problem seems, however, lie not in the firmware, but in your hardware - or at least in the way it is handled by Odin or drivers. Note that *.tar.md5 archive contain md5 checksum concatenated to the very end of archive. When you're selected firmware file in Odin (in a PDA section), it probably took a longer while before the file appeared as selected - this is because meanwhile Odin is checking the checksum (and for that purpose, he has to read whole 1.5Gig file...). So: If Odin allowed you to flash the tar.md5 file - then it was NOT corrupted, otherwise it won't even be possible to start the process as of file wrong checksum!
4. THere is another possibility - that something bad happened to your pit section (it has been overwritten in result of flashing firmware for a wrong device) and your nand partition table is corrupted, which may probably result in an impossibility of flashing files or impossibility of mounting filesystems... I cannot help then, I have never faced such a problem in practice myself.
5. Pt 4, however, seems to be less possible than pt 3.
- Have you ever flashed any firmware with success?
- what do you mean by "long installation process"? A 10 minutes? An hour? Half-a-day?
- Have you been observing Odin while flashing? It's indicating which partition is being flashed atm - can you tell on which firmware part (system? hidden? cache?) did it fail?
- Try using different version of Odin (an older one, guess 3.07? not sure however - the one which has "PDA" section instead of a single-letter names)
- Try flashing from different PC
- use usb 2.0 port instead of 3.0 ones.
- try using different usb cable (I guess it'll may be the hardest thing to check because the cable seem to be quite unique )

Grateful to you...
esgie said:
1. You may want to try using:
http://samsung-updates.com/
instead of samfirmware, if you're experiencing corrupted downloads from the latter (but it's not very probable... see pt 3)
2. At the moment I am testing new firmware revision, downloaded from samsung-updates: P905XXUAND1 for NEE region. It flashed fine. Also, for most of the time I have used P905XXUANC3 firmware for DBT region (Germany - even if I am not a German, I do not really care about csc stuff, and I got used to the fact that the newest firmwares were always released for DBT region first on my old "standard" Note 10.1). It was flashing fine, too.
3. The problem seems, however, lie not in the firmware, but in your hardware - or at least in the way it is handled by Odin or drivers. Note that *.tar.md5 archive contain md5 checksum concatenated to the very end of archive. When you're selected firmware file in Odin (in a PDA section), it probably took a longer while before the file appeared as selected - this is because meanwhile Odin is checking the checksum (and for that purpose, he has to read whole 1.5Gig file...). So: If Odin allowed you to flash the tar.md5 file - then it was NOT corrupted, otherwise it won't even be possible to start the process as of file wrong checksum!
4. THere is another possibility - that something bad happened to your pit section (it has been overwritten in result of flashing firmware for a wrong device) and your nand partition table is corrupted, which may probably result in an impossibility of flashing files or impossibility of mounting filesystems... I cannot help then, I have never faced such a problem in practice myself.
5. Pt 4, however, seems to be less possible than pt 3.
- Have you ever flashed any firmware with success?
- what do you mean by "long installation process"? A 10 minutes? An hour? Half-a-day?
- Have you been observing Odin while flashing? It's indicating which partition is being flashed atm - can you tell on which firmware part (system? hidden? cache?) did it fail?
- Try using different version of Odin (an older one, guess 3.07? not sure however - the one which has "PDA" section instead of a single-letter names)
- Try flashing from different PC
- use usb 2.0 port instead of 3.0 ones.
- try using different usb cable (I guess it'll may be the hardest thing to check because the cable seem to be quite unique )
Click to expand...
Click to collapse
Dear Sir,
I am so surprised to see that somebody response me for the core of his heart! I am so pleased to realize that some body look at my problem very attentively! sir, thank you!
so,
** I have tried using different usb cable to flash
** I have tried both 3.9 or 3.7 odin
** I have tried different pc to flash
** I have used 2.0 or 3.0 both usb cable
** I have tried both kies3 or previous kies
** I am giving here the whole odin texts which
was shown
"<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> aboot.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> sdi.mbn
<ID:0/008> NON-HLOS.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!"
** Long installation process means 5-7 minutes! (I think it is normal, sorry)
** yes, I have used all high end android devices and all was rooted, installed cwm recovery, custom room, so I have experience well on android I am not new to play with android operating system. even now I am also using Note 3 with Omega custom rom and working great.
** I am thinking may be the problem is about pit. and I don't know where I will find a .pit file for SM-P905. some how may be the pit of my note pro is corrupted. i don't know actually I am not a developer!
Here all you wanted to know!
Dear Sir please help me to make alive my Galaxy Note Pro!
Please!!!

screen shot!
after the failed flashing operation all the time my devices shows, i am giving a screen shot!

Downloaded 3 Firmware
Already I have downloaded 3 rom, (because I thought the firmware file was corrupted) but by studying your post I know now when ever odin accept any firmware that means the rom file is not corrupted! thanks!
P905XXUANAE_P905DBTANA6_DBT.zip
P905XXUANAE_P905OXXANA7_BTU.zip
P905XXUANC3_P905BTUAND2_BTU.zip
i have download this 3 files!

Ok, we shall try to flash firmware otherwise, using more advanced method.
Note that if ur knox isn't yet tripped - it WILL trip it, breaking your warranty (in this case it's better to send the device to service center - i suppose something's broken...). If it is tripped, you have nothing to lose...
1. Download:
http://www67.zippyshare.com/v/25492738/file.html
do not rename the file, it should be named recovery.img
2. Using this tool
http://forum.xda-developers.com/showthread.php?t=2446269
convert provided recovery.img to tar.md5 format
3. Flash it with odin (it should take a few sec to finish and it should succeed as recovery seems to flash ok on your device)
4. Enter recovery mode by holding power+home+vol up. Warning should appear about warranty and then custom recovery should appear on screen..
5. Using touch menu seek thru options and thru wipe menu format the system partition, as well as wipe/format data and cache (any errors?). Leave the device for a moment...
6. Simultanously, open one of 2+ gig tar.md5 firmwares (i recommend to choose one which you tried to flash with odin in your last trial) downloaded from sammobile with winrar or 7zip (if error about bad end of file appears ignore it) and extract system.img.ext4 somewhere...
7. Download simg2img from post #19
http://forum.xda-developers.com/showthread.php?t=2191930&page=2
and use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)
8. Copy system.img to root of empty micro sd card (fat32 or exfat formatted). Check if it has been copied correctly. Put the micro sd card into device. Reboot recovery once again
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!!! Also, process may take a LONGER while, like 10 mins, its ok, even if there is no progress indicator. Youll know it finished when keyboard will show back again (any errors here??)
10. Reboot AGAIN to recovery, go to Mounts menu, tick system, data and cache (does tick within system work?)
11. Go to terminal as in pt 9, but this time enter:
restorecon -R /cache
restorecon -R /data
restorecon -R /system
(errors?)
12. Reboot into system and cross yer fingers

mismatch
esgie said:
Ok, we shall try to flash firmware otherwise, using more advanced method.
Note that if ur knox isn't yet tripped - it WILL trip it, breaking your warranty (in this case it's better to send the device to service center - i suppose something's broken...). If it is tripped, you have nothing to lose...
1. Download:
http://www67.zippyshare.com/v/25492738/file.html
do not rename the file, it should be named recovery.img
2. Using this tool
http://forum.xda-developers.com/showthread.php?t=2446269
convert provided recovery.img to tar.md5 format
3. Flash it with odin (it should take a few sec to finish and it should succeed as recovery seems to flash ok on your device)
4. Enter recovery mode by holding power+home+vol up. Warning should appear about warranty and then custom recovery should appear on screen..
5. Using touch menu seek thru options and thru wipe menu format the system partition, as well as wipe/format data and cache (any errors?). Leave the device for a moment...
6. Simultanously, open one of 2+ gig tar.md5 firmwares (i recommend to choose one which you tried to flash with odin in your last trial) downloaded from sammobile with winrar or 7zip (if error about bad end of file appears ignore it) and extract system.img.ext4 somewhere...
7. Download simg2img from post #19
http://forum.xda-developers.com/showthread.php?t=2191930&page=2
and use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)
8. Copy system.img to root of empty micro sd card (fat32 or exfat formatted). Check if it has been copied correctly. Put the micro sd card into device. Reboot recovery once again
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!!! Also, process may take a LONGER while, like 10 mins, its ok, even if there is no progress indicator. Youll know it finished when keyboard will show back again (any errors here??)
10. Reboot AGAIN to recovery, go to Mounts menu, tick system, data and cache (does tick within system work?)
11. Go to terminal as in pt 9, but this time enter:
restorecon -R /cache
restorecon -R /data
restorecon -R /system
(errors?)
12. Reboot into system and cross yer fingers
Click to expand...
Click to collapse
according to your link there is no file, named "recovery.img" but the file name is "libwfdsm.so"

DAAAAMN wrong link copied.
Wait a sec, I'll upload it in a while. Until then, you may start doing steps 6-8.
EDIT:
Here u go
http://www47.zippyshare.com/v/40021725/file.html
PS: using above method (a similiar one, to be exact...), figured out on my own to be exact, I have managed to unroot and revert to fully-stock state my old Note10.1, which I was not able to flash straight via Odin at all because the port's been broken, so I was able to send it to service center without any worries (at least related to the possibility of detecting the customization by the service) The difference is that you are able to flash files via Odin - except the system - but also that my device was booting at the very beginning, and yours not. Neverthless, with appropriate modifications, it should work on P905 too - or at least explain what's the reason of your issues.
Don't want to worry you, but as of now i am considering physical NAND damage as the most possible cause of the issue... But that's a theory only. Good luck.

problem solved!
esgie said:
DAAAAMN wrong link copied.
Wait a sec, I'll upload it in a while. Until then, you may start doing steps 6-8.
EDIT:
Here u go
http://www47.zippyshare.com/v/40021725/file.html
PS: using above method (a similiar one, to be exact...), I managed to unroot and revert to fully-stock state my old Note10.1, which I was not really able to flash straight via Odin because the port's been broken. The difference is that you are able to flash files via Odin - except the system - but also that my device was booting at the very beginning, and yours not. Neverthless, with appropriate modifications, it should work on P905 too - or at least explain what's the reason of your issues.
Don't want to worry you, but as of now i am considering physical NAND damage as the most possible cause of the issue... But that's a theory only. Good luck.
Click to expand...
Click to collapse
my dear sir, don't know how but my note pro start up automatically. before some minutes on my display "unauthorized operation occur, please restart you device" was showing. so after pressing ok, device tried to restart but it was stuck on recovery mode. so i started my device manually. when I pressed reboot from recovery everything was fine and still now it is working properly!
I don't know is going gone on my device. but is a mystery for me!
one thing, after trying to fix my devices long time my note pro battery was empty and i could not able to charge because it was stuck on download mode. after searching i got a boot image.tar.md5 for SM-P905. and install that Samsung logo appear, and device started charging. and after charge a few, It was start up!
now when I am connecting it with my pc, kies says I need to update my device. but previously my device was updated the latest software. I am giving the screen shot!
what will I do now? just update via kies and star to operate my device normally?

ornobohornish said:
my dear sir, don't know how but my note pro start up automatically. before some minutes on my display "unauthorized operation occur, please restart you device" was showing. so after pressing ok, device tried to restart but it was stuck on recovery mode. so i started my device manually. when I pressed reboot from recovery everything was fine and still now it is working properly!
I don't know is going gone on my device. but is a mystery for me!
one thing, after trying to fix my devices long time my note pro battery was empty and i could not able to charge because it was stuck on download mode. after searching i got a boot image.tar.md5 for SM-P905. and install that Samsung logo appear, and device started charging. and after charge a few, It was start up!
now when I am connecting it with my pc, kies says I need to update my device. but previously my device was updated the latest software. I am giving the screen shot!
what will I do now? just update via kies and star to operate my device normally?
Click to expand...
Click to collapse
Did I understood well that after emptying the battery of the non-working device out and recharging it back again at least a little, the device started to work again? Seems like... eeee...? some voltage circulating through the mainboard was the cause?
Well, I bet it was faulty or somehow corrupted boot.img (as it was the only partition you have flashed between the time the device seemed damaged and time the device started to work again), but I am not sure what really happened.
As to the firmware update question: from the screenshot attached I can see that you are now running XXUNAE firmware. Proposed XXUNC3 is a newer one so in general it is recommended to do the update. However, we cannot be sure anyhow if your device will not react in a same way as before. However, current updates seems to be minor ones (they concentrate on security policies and not on features...) so my recommendation is to leave it alone, at least until some more important update...

ohh nooo! befor reading you reply I was tried to update my device by kies. but same thing happen here. stuck on Invalid ext4 image!

i am so tired
esgie said:
Did I understood well that after emptying the battery of the non-working device out and recharging it back again at least a little, the device started to work again? Seems like... eeee...? some voltage circulating through the mainboard was the cause?
Well, I bet it was faulty or somehow corrupted boot.img (as it was the only partition you have flashed between the time the device seemed damaged and time the device started to work again), but I am not sure what really happened.
As to the firmware update question: from the screenshot attached I can see that you are now running XXUNAE firmware. Proposed XXUNC3 is a newer one so in general it is recommended to do the update. However, we cannot be sure anyhow if your device will not react in a same way as before. However, current updates seems to be minor ones (they concentrate on security policies and not on features...) so my recommendation is to leave it alone, at least until some more important update...
Click to expand...
Click to collapse
emergency firmware recovery start on kies but also stuck on "invalid ext4 image" and my my pc says to go service center! giving two screen shot!

ornobohornish said:
emergency firmware recovery start on kies but also stuck on "invalid ext4 image" and my my pc says to go service center! giving two screen shot!
Click to expand...
Click to collapse
My recommendation: repeat the procedure Ive posted earlier. Well se what happens
It looks like some part of your nand may be physically corrupted... and unwriteable.

before closing my notebook I am just hit the "CF-Auto-Root-viennalte-viennaltexx-smp905.tar" and surprisingly saw after successfully install the root file by Odin, my device start-up again. but problem is "unfortunately Samsung keyboard stopped" sowing. so I have install google stock keyboard and without Samsung keyboard it is running properly. though it is now working properly without samsung keyboard but I am little bit unhappy with my new Note Pro, I have just purchased this 3-6-14 and to day 5-6-14. I can not even look at thish properly because after purchasing it is disturbing! many thanks dear sir!
now I will try again with your instruction!

can not find "simg2img"
esgie said:
Ok, we shall try to flash firmware otherwise, using more advanced method.
Note that if ur knox isn't yet tripped - it WILL trip it, breaking your warranty (in this case it's better to send the device to service center - i suppose something's broken...). If it is tripped, you have nothing to lose...
1. Download:
http://www67.zippyshare.com/v/25492738/file.html
do not rename the file, it should be named recovery.img
2. Using this tool
http://forum.xda-developers.com/showthread.php?t=2446269
convert provided recovery.img to tar.md5 format
3. Flash it with odin (it should take a few sec to finish and it should succeed as recovery seems to flash ok on your device)
4. Enter recovery mode by holding power+home+vol up. Warning should appear about warranty and then custom recovery should appear on screen..
5. Using touch menu seek thru options and thru wipe menu format the system partition, as well as wipe/format data and cache (any errors?). Leave the device for a moment...
6. Simultanously, open one of 2+ gig tar.md5 firmwares (i recommend to choose one which you tried to flash with odin in your last trial) downloaded from sammobile with winrar or 7zip (if error about bad end of file appears ignore it) and extract system.img.ext4 somewhere...
7. Download simg2img from post #19
http://forum.xda-developers.com/showthread.php?t=2191930&page=2
and use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)
8. Copy system.img to root of empty micro sd card (fat32 or exfat formatted). Check if it has been copied correctly. Put the micro sd card into device. Reboot recovery once again
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!!! Also, process may take a LONGER while, like 10 mins, its ok, even if there is no progress indicator. Youll know it finished when keyboard will show back again (any errors here??)
10. Reboot AGAIN to recovery, go to Mounts menu, tick system, data and cache (does tick within system work?)
11. Go to terminal as in pt 9, but this time enter:
restorecon -R /cache
restorecon -R /data
restorecon -R /system
(errors?)
12. Reboot into system and cross yer fingers
Click to expand...
Click to collapse
dear sir,
in your link nowhere i found "simg2img"! I searched all the page number 9 but no where I found "simg2img"!!!
help please
---------- Post added at 10:28 AM ---------- Previous post was at 10:01 AM ----------
able to download simg2img from this link: http://web.djodjo.org/?a=download:android:tools:x86_linux:ext4tools
but how to use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)?
how to use simg2img?

Will this work with the SM-P900?
esgie said:
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!
Click to expand...
Click to collapse
Hi Esgie.
I'm assuming that most of this would work for the SM-P900 (wifi only) version too? What would I use for the dd command in step 9?
Thanks for your help.
Jo Pop

ornobohornish said:
before closing my notebook I am just hit the "CF-Auto-Root-viennalte-viennaltexx-smp905.tar" and surprisingly saw after successfully install the root file by Odin, my device start-up again. but problem is "unfortunately Samsung keyboard stopped" sowing. so I have install google stock keyboard and without Samsung keyboard it is running properly. though it is now working properly without samsung keyboard but I am little bit unhappy with my new Note Pro, I have just purchased this 3-6-14 and to day 5-6-14. I can not even look at thish properly because after purchasing it is disturbing! many thanks dear sir!
now I will try again with your instruction!
Click to expand...
Click to collapse
I had same problem, install rom from greece. Some roms from sammobile and samsung firmware are giving errors, I have tested polish and british giving "odin: invalid ext4 image" error. After installing greece one everything works flawlessly, samsung keyboard also.

Root tutorial for intel atom Cherry Trail dual os tablet

root tutorial using onda v820w ch v1 for example :
--root tools (root.zip) , unzip to c:\
https://drive.google.com/file/d/0BySA4DPrnBM-eXpsdlFzN21jQm8/view?usp=sharing
or
link：http://pan.baidu.com/s/1pLjJhHp
pwd：h79i
--use cmd and BOOTIMG.EXE to unpack boot.img
bootimg.exe --unpack-bootimg
-- use notepad++ open file \initrd\init*.rc , maybe called init.aosp.rc
--search string "class_start core" , add one line on this line's top
start sysinit
-- and then add these lines to bottom and save
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
-- find another file called default.prop
modify ro.secure=1 to ro.secure=0
--use cmd and bootimg.exe to repack boot.img
bootimg.exe --repack-bootimg
rename boot-new.img to boot.img
after successfully boot into android , go to developer enable OEM Bootloader Lock and usb debug mode
download lastest supersu TWRP / FlashFire installable ZIP , copy to emmc flash or microsd card
http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
unzip root.zip to c:\
-- install driver follow this order and new driver overwrite old driver
iSocUSB-Driver-Setup-1.2.0.exe
IntelAndroidDrvSetup1.5.0.exe
PhoneFlashTool_5.3.2.0_win32.exe
connect otg usb line and hold "volume-" restart tablet or you can find reboot app to enter fastboot mode
cmd run
fastboot flash boot boot.img
fastboot oem unlock
fastboot reboot
hold "volume-" and enter fastboot mode again
-- if twrp file is not working on your tablet , you can find others twrp version , you need try more by yourself
v820w ch twrp file : I use v919 ch twrp on xda forum , rename to twrp.img
--cmd run to enter twrp recovery mode , if tablet don't automatically to restart to enter recovery , you can use volume key to select recovery mode and power key to ensure
fastboot boot twrp.img
connect mouse because touch fuction maybe not work , twrp install supersu recovery zip , root finish
you can use app like foldermount now
if play store has new version supersu , you can update app
but you can't install "binary" from app , it will damage system , if you do , you will find microsd size always 1GB max
so , how to install supersu "binary" , you only need use above step about flash twrp and install lastest recovery zip , after install lastest supersu zip file , on table you run supersu , it will not show any update "binary" request .
p.s. Onda Table Full Gapps Firmware
http://forum.xda-developers.com/android/development/onda-table-gapps-firmware-root-tutorial-t3462774
dual os tablet can use 64gb/128gb microsd card , you need use GUIformat to format to FAT32
dual os all can read/write it
if you have highspeed microsd compatible issue
I suggest you can buy speed < 50 mbps/s sandisk microsd
it work fine on onda tablet
on windows , you can use micorsoft official download win10 version to install
for example onda tablet , you need to do two things
1. backup driverstroe \ FileRepository , after reinstall new win10 , you can use device manager to find lose drivers .
2. backup \system32\drivers\sileadtouch.fw , you need to copy this touch location driver to new win10 .
win10 touch gamepad
china version is free , you don't need to pay to buy 8-axis , function is useless :
https://www.microsoft.com/zh-tw/store/p/微派平板助手/9nblgggzlx51
guide translation here , look attachments pictures : http://forum.xda-developers.com/windows-8-rt/general/tutorial-onsceen-gamepad-touchpad-t3104501
english version is free to try :
https://www.microsoft.com/zh-tw/store/p/touch-anyway/9nblggh31d54

Thank you so much for this detailed guide!
I am having some troubles at the line "fastboot flash boot boot.img": I get "FAILED (remote: Flash failure: Not Found)" on the computer, and "Failed to get partition [the_name]: Not Found" on the tablet screen.
Does anyone know something about this error?
Thanks!

Thanks you for the post! Any idea if I can use this same process to root RemixOS 2.0 on an Onda Obook 11 Plus? I downloaded the RemixOS .zip for the Obook 11 Plus from the Onda site and it seems like the contents are very similar to the process that you describe here...
Or - do you know if I can somehow "convert" the RemixOS partition to run stock Android 5.1? I know that they sell this same device with stock Android as well, but I didn't see an Android .zip file on the Onda site for this device - just the RemixOS .zip file...
Thank you!
Sent from my OBOOK 11 PLUS DUALOS using Tapatalk

Well, not so worried about root now. i already broke my new toy... Was messing with the BIOS brightness level settings (get get lower brightness in RemixOS) and accidentally set GOP Driver to "Disabled" in the BIOS - not I can't get ANY output on the screen or via the HDMI out.. Tried *everything* to try and reset it "blindly", but no luck.. If anyone has any ideas (like how to flash a new BIOS or reset it to defaults), please chime in! Frustrated...
Onda Obook 11 Plus.
Thanks.
Sent from my HP SlateBook 10 x2 PC using Tapatalk

Dificulty
Man, i'm having too much problems to understand exactly what i have to do. I have panic to do something wrong. If you can add some screenshots to post will save my life and my dumbness hahahahah
Thanks a lot

hey i no a way to fix this problem it will cost a little about £10 maybe you need to buy a ch341a flash tool off ebay and the 8 pin clip you will need a computer to plug it into and also your bios .bin file.open up your tablet find the bios chip put the clip on run software load your bios.bin and write it to the chip with software all done good luck

[email protected] said:
hey i no a way to fix this problem it will cost a little about £10 maybe you need to buy a ch341a flash tool off ebay and the 8 pin clip you will need a computer to plug it into and also your bios .bin file.open up your tablet find the bios chip put the clip on run software load your bios.bin and write it to the chip with software all done good luck
Click to expand...
Click to collapse
Thanks - Yeah, I'm aware of that method to re-flash the BIOS, but I have 2 issues with that:
1. Trying to get the damn tablet apart without breaking anything (there isn't a single screw involved here). Considering the cheap materials used on these tablets to begin with, I'd be lucky to get it apart without breaking anything - and honestly, don't really feel like fighting it.
2. More importantly, the BIOS for this device is not available anywhere. The manufacturer has never released it. So if even if I did manage to get the device apart without breaking it, I'd have no BIOS file to flash anyway.
For what I paid for it, I'll write it off as a learning experience and move on. Truth is that I've found a much better device anyway (Chuwi HI10 Pro/Plus). The Onda was OK, but the Chuwi's are MUCH better devices.
But again, thanks for the info - I do appreciate it.
Sent from my Vi10 Plus using Tapatalk

i rooted my onda v80 plus successfully, but now there is no way to access windows again. can anybody tell me how i access windows?
There is no "OS Change" In the android system, the tablet recognices no volume + at the starting process, so i have no chance...

kudi120 said:
i rooted my onda v80 plus successfully, but now there is no way to access windows again. can anybody tell me how i access windows?
There is no "OS Change" In the android system, the tablet recognices no volume + at the starting process, so i have no chance...
Click to expand...
Click to collapse
You can try going in to your bios and check boot mode to see if it says android or windows

I don't know where to start.
I have Cube iwork 8 air. Trying to root but where can i find bootimg which i have to unpack.
Unpacked twrp.img and found init.rc but cannot find line with class_start core, all i have is class_start default#. Is it place where i have to add start sysinit? Where exactly?
Can someone add those lines to file and ad here?
Please explain this as for total noob. Cause for me it looks too complicated like i should do something before which is not include in this tutorial.
Tried iroot, kingroot and this https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 method as well, no luck so far.
Thank You in advance.

You can boot Linux or Windows and make a dump of boot partition.

Repacking boot.img error
wgarnett said:
root tutorial using onda v820w ch v1 for example :
]
Click to expand...
Click to collapse
Hi,
I have the onda obook 10 boot.img. Unpacking goes on well including adding the lines instructed using the notepad ++. Repacking however produces the error "set_cmdline <>takes exactly 1 argument <6 given>".
What could I be doing wrong?

First - there is no need to quote the OP fully.
Please upload or attach the 2 original and your 2 changed files (and original boot.img), I will take a look.

Troubles repacking the onda obook 10 boot.img
wgarnett said:
root tutorial using onda v820w ch v1 for example :
]
Click to expand...
Click to collapse
Hi there,
Tried the above rooting method but have a problem repacking the boot image. I get the error "cmdline too many arguments (6 given)". I unpacked stock android boot.img tweaked it and flashed but the tab never booted.
Kindly help

Ivansu said:
Hi there,
Tried the above rooting method but have a problem repacking the boot image. I get the error "cmdline too many arguments (6 given)". I unpacked stock android boot.img tweaked it and flashed but the tab never booted.
Kindly help
Click to expand...
Click to collapse
I already answered you just above your post.
And again, please don't quote the WHOLE message, it is unneeded.

The excessive note on quoting is appreciated. I will take a look on the newbies guide. Attached are the original and modified files. The boot.img size is more than the limit allowed.
Here is the link on Google drive.
https://drive.google.com/file/d/0B7mm7XsgjszUZEY3VEM4ZEVObGc/view?usp=sharing
Thanks

Ivansu said:
The excessive note on quoting is appreciated. I will take a look on the newbies guide. Attached are the original and modified files.
Click to expand...
Click to collapse
modified_files.rar contains no files.

My bad for that. I have it right now

Your changes to default.prop are OK. To init.aosp.rc not:
class_start core
+
+ start sysinit
+ service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
+ disabled
+ oneshot
While I did it like this:
+ start sysinit
class_start core
+ service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
+ disabled
+ oneshot
+ means added lines.
Does it work if you move "start sysinit" before "class_start core"?

Thank you for pointing that error. I modified but still have the same repack error. See the attachment