[Q] Unsupported devices for rooting and Cyanogen mod - General Questions and Answers

Hello forum, I am kind of new to android and I just purchased my first device, the Curtis KLU 7028 tablet, out of the box it runs 2.1 and I was wondering if I could fix that to run a custom ROM like Cyanogen Mod, but alas, all rooting attempts seem to go through but no super user or other root effects are noticed, I downloaded the superuser app myself after several failed root attempts but it says "An error occurred and su was not updated. A zip file ... has been placed on your sdcard please reboot in recovery mode and flash it to upgrade our su binary" the manual says to hold the esc key while rebooting and connect to computer for recovery but I have no clue what to do from there, also I cannot find any custom roms for this model, it has a trackball mini hdmi out mini usb full usb host power key menu key mic/reset and I wanted to see if there were any compatible ROMs to use and make it run faster or just remove the bloatware
Thank you all for your other threads which I have read avidly and let me know if you can help

On the Curtis International web site (google it, I can't post outside links, yet) is a firmware upgrade. This upgrade will load a file known as "upgrade.img" to the device, adding access to the Android market, etc. There is a program included in the firmware zip file which will do this. I'm going to try to load an img file of my own by replacing the included one.

Related

[Q] Root didn't stick, went back to stock, now US Wifi Xoom won't OTA update

(Sorry if this has been asked before, I've been searching for hours and I know there is an active thread that is similar but it turns out those aren't US Xooms, they are German according to the OP)
Background: I have a wifi US xoom that I bought on launch day (so I know it's US, MZ604). I'm experienced enough to mostly know what I'm doing, though I'm definitely no expert. I owned a D1 from the day it came out until the day the D4 was released, I rooted the D1 immediately using terminal and adb before any "fast" roots were achieved. I'm comfortable in adb and fastboot.
With my xoom, I was so happy with stock that I decided to wait to root it (like an idiot), and didn't try until about two weeks ago. By this time I already had all the OTA updates including ICS.
Long story short, I couldn't get root to "stick". I flashed CWM, was able to get the universal xoom root to work, installed the EOS rom, booted, and played around with root. Used Titanium and whatnot. Upon reboot, superuser was still there and still said access was granted to a few programs (Titanium specifically) but the system no longer had root access (Titanium and other apps like Root Explorer/ES File Explorer reported back "no root").
I decided to start fresh. Got the stock img files from moto's site. Pushed them all via fastboot (including recovery) and returned to stock 3.0.1. I'm trying to use this thread to root it, which says to let the OTA updates bring it up to 3.2 - however here's my problem:
The System Updates screen keeps saying "your system is up to date!" but my About Tablet screen says "Android version 3.0.1" and "Build HWI69". Wifi is connected fine; my browser works. Soooo...why won't it recognize that I'm on 3.0.1 and offer me the various system updates that came after HWI69? I tried all the tricks I found online including setting my system date ahead a few days, but none of that helped. Should I just wait overnight and see if it happens or is this a bug someone has seen before?
tl;dr version:
US Wifi Xoom on 3.0.1 stock (HWI69) via Motorola's stock img files, connected to wifi, will not recognize that there are system updates in About > System Updates. Why?
[CONFIRMED] Manually Update to 3.2 on US WiFi Xoom
Just followed the steps over at Manual Update to 3.2 on a Stock 3.1 Xoom, Non-rooted method.
The process was fast and easy, but requires:
•Honeycomb 3.1 to be installed
•USB OTG cable
•Flash Drive
•3.2 Update
Try this at your own risk, but it worked well on the two Xooms This method requires an OTG Cable.
DO NOT TRY THIS ON YOUR 3G XOOM!
I know it works as long as you are on 3.1 already.
1. Acquire an OTG Cable and a USB Thumb Drive, Copy the 3.2 stock image and rename it as update.zip. Plug the OTG cable into your Xoom with the thumb drive attatched, OR you can place this file on your external SDcard.
2. Reboot your Xoom.
3. Once the dual core screen comes up, tap the volume down button repeatedly until you get menu options.
4. Select Android Recovery and press the volume up button.
5. At green android, hold the power button and tap the volume up button once, release the power button.
6. Select the Apply Update option, and choose the correct file from the USB Drive OR you External SDcard. Tap the power button to continue.
7. Let it run through the update process, choose reboot once it is complete, and enjoy!
The 3.2 stock image file can be found here: HTJ85B.zip http://www.mediafire.com/?8n5o9a3xianyen6 or Here: http://www.multiupload.com/FUNSHXJSGT
While it worked fine for others, you are responsible for your own device. Enjoy!
UPDATE: Some have reported that this method works with update.zip on an SD card as well!
As always, If This Was Helpful Hit The Thanks!

[q] huawei u8812d

Can I root Huawei U8812D? pls someone advice me.
babbird said:
Can I root Huawei U8812D? pls someone advice me.
Click to expand...
Click to collapse
I am a new user so I cannot post a links yet but google your phone and there should be a link to ANDROID net forum. There you will find a video showing you how to do it.
found something on chinese site that looks good
babbird said:
Can I root Huawei U8812D? pls someone advice me.
Click to expand...
Click to collapse
This looks really rough, but apparantly there is a boot.img, then other cracking tools can be used.
I'd love to try it, but... well... my chinese is limited to google-translate.
The URL won't post so this is a big hint:
products . mobileuncle . com / thread-202642-1-1 . html
I think I got it root on g302d u8812d
j_chytown said:
This looks really rough, but apparantly there is a boot.img, then other cracking tools can be used.
I'd love to try it, but... well... my chinese is limited to google-translate.
The URL won't post so this is a big hint:
products . mobileuncle . com / thread-202642-1-1 . html
Click to expand...
Click to collapse
Currently on that URL is a approx 14 MB rar file download, I _think_ I just got it sorted!
I don't have time now to make this pretty, but some others who want to hack. add links, etc feel free to work with this...
in fact I dont know if all these steps are required.
General Broad steps (ymmv, you are doing this to your own dang phone, dont blame me for bricks viruses or earthquakes etc, etc/ etc).
on your computer, uninstall adb, pdanet and any other tools that use the adb drivers and dlls, reboot as needed.
install the mt6575 drivers (I forgot whether I downloaded these or if they were part of the 14 meg file) reboot as needed
power down phone.
remove battery from phone, don't plug into computer.
launch flash_tool.exe
load the included scatterloading file MT6575...emmc.txt
press the download button
plug in phone to usb
put battery in phone
watch the blinkinlights for a few seconds, wait for the big green O
then I disconnect phone and ensure power down.
install SDK
power up phone and plug in
test adb (adb shell)
kill adb server
download and install superoneclick
download extra superoneclick exploits
launch superoneclick
click the big root button.
Test (you can use something like rom manager)
Now people should be able to try to install various CWMs.
I haven't gotten that far yet.
CWM for u8812d g302d ?
j_chytown said:
Currently on that URL is a approx 14 MB rar file download, I _think_ I just got it sorted!
I don't have time now to make this pretty, but some others who want to hack. add links, etc feel free to work with this...
in fact I dont know if all these steps are required.
General Broad steps (ymmv, you are doing this to your own dang phone, dont blame me for bricks viruses or earthquakes etc, etc/ etc).
on your computer, uninstall adb, pdanet and any other tools that use the adb drivers and dlls, reboot as needed.
install the mt6575 drivers (I forgot whether I downloaded these or if they were part of the 14 meg file) reboot as needed
power down phone.
remove battery from phone, don't plug into computer.
launch flash_tool.exe
load the included scatterloading file MT6575...emmc.txt
press the download button
plug in phone to usb
put battery in phone
watch the blinkinlights for a few seconds, wait for the big green O
then I disconnect phone and ensure power down.
install SDK
power up phone and plug in
test adb (adb shell)
kill adb server
download and install superoneclick
download extra superoneclick exploits
launch superoneclick
click the big root button.
Test (you can use something like rom manager)
Now people should be able to try to install various CWMs.
I haven't gotten that far yet.
Click to expand...
Click to collapse
Okay I may have found a working CWM clockworkmod recovery, but I don't have access to the chinese site, so others out there may be able to download it and try it out.
mm-mpxteam . net / forum . php ? mod = viewthread & tid = 4203
or maybe this one:
products . mobileuncle . com / thread-203098-1-1 . html
got the uncles recovery on the phone!
j_chytown said:
Okay I may have found a working CWM clockworkmod recovery, but I don't have access to the chinese site, so others out there may be able to download it and try it out.
mm-mpxteam . net / forum . php ? mod = viewthread & tid = 4203
or maybe this one:
products . mobileuncle . com / thread-203098-1-1 . html
Click to expand...
Click to collapse
it isn't clockwork, but I got a mobileuncle recovery on the phone. Is kinda fun to try to translate!
pan . baidu . com / share / link ? shareid = 63706 & uk = 2483368669
---------- Post added at 06:39 PM ---------- Previous post was at 06:25 PM ----------
j_chytown said:
it isn't clockwork, but I got a mobileuncle recovery on the phone. Is kinda fun to try to translate!
pan . baidu . com / share / link ? shareid = 63706 & uk = 2483368669
Click to expand...
Click to collapse
installed gapps 20110828 (via mobileuncle recovery) and I now have a market that doesn't force-close!
still getting "partners" to force close, but a lot of other stuff is working.
Great work!!! I'll try this on my phone or wait until is working?
Are the recovery and rom in chinese?
Thank a lot for testing.
working well
hiosin said:
Great work!!! I'll try this on my phone or wait until is working?
Are the recovery and rom in chinese?
Thank a lot for testing.
Click to expand...
Click to collapse
It is working very well.
No need for you or anyone to wait.
Just please know what you are doing (do you have basic understanding of recovery mode, roms, factory mode, and the dangers) in other words, if this is your first time doing this on a phone.. ask someone who knows what they are doing for help because I am not able to put together a documented procedure, but the findings above should allow someone else to do that. Additionally, I have no idea of the legality or safety of the software at URLs above.
conceptually this is 4 steps
1) flash boot.img that will allow cracking
2) crack to get SU installed
3) install Mobile Uncle Recovery mode and app
4) install gapps.
The MobileUncle recovery mode is Chinese, But the mobileuncle app is kinda like rom manager, it lets you set up what happens at next boot so you don't need to read the chinese in recovery text mode.
The patched rom is working for me in English with root, no detectable problem except FC on google partners (and I can't tell if that actually does anything). Remember this is not a new rom, just a patch to the huawei rom that allows a root crack.
There are about 4 chinese apps that I am afraid to uninstall..
one appears to be a chinese app store too, kinda fun to browse
gapps must be flashed with mobileuncle recovery (don't just unzip them)
US google play store is working.
I am fully migrated to this phone now and use it for daily work.
Good luck, and remember that this is why you got an android instead of a i-Thing.
Thanks thanks again. I'll try it and don't worry this is not the first time to modify a mobile. If it is all ok i posted here.
Working u8812d
Ok... It was successfully working on my phone. I have root and change recovery and then installing gapps. Almost of the apps is working of the play store. Thanks again and hope there is a release of ICS or JB rom for our phones.
See ya!!!:good:
j_chytown said:
It is working very well.
No need for you or anyone to wait.
Just please know what you are doing (do you have basic understanding of recovery mode, roms, factory mode, and the dangers) in other words, if this is your first time doing this on a phone.. ask someone who knows what they are doing for help because I am not able to put together a documented procedure, but the findings above should allow someone else to do that. Additionally, I have no idea of the legality or safety of the software at URLs above.
conceptually this is 4 steps
1) flash boot.img that will allow cracking
2) crack to get SU installed
3) install Mobile Uncle Recovery mode and app
4) install gapps.
The MobileUncle recovery mode is Chinese, But the mobileuncle app is kinda like rom manager, it lets you set up what happens at next boot so you don't need to read the chinese in recovery text mode.
The patched rom is working for me in English with root, no detectable problem except FC on google partners (and I can't tell if that actually does anything). Remember this is not a new rom, just a patch to the huawei rom that allows a root crack.
There are about 4 chinese apps that I am afraid to uninstall..
one appears to be a chinese app store too, kinda fun to browse
gapps must be flashed with mobileuncle recovery (don't just unzip them)
US google play store is working.
I am fully migrated to this phone now and use it for daily work.
Good luck, and remember that this is why you got an android instead of a i-Thing.
Click to expand...
Click to collapse
This does not work for my u8812d, gives an error using flash tool
Still not rooting
j_chytown said:
Currently on that URL is a approx 14 MB rar file download, I _think_ I just got it sorted!
I don't have time now to make this pretty, but some others who want to hack. add links, etc feel free to work with this...
in fact I dont know if all these steps are required.
General Broad steps (ymmv, you are doing this to your own dang phone, dont blame me for bricks viruses or earthquakes etc, etc/ etc).
on your computer, uninstall adb, pdanet and any other tools that use the adb drivers and dlls, reboot as needed.
install the mt6575 drivers (I forgot whether I downloaded these or if they were part of the 14 meg file) reboot as needed
power down phone.
remove battery from phone, don't plug into computer.
launch flash_tool.exe
load the included scatterloading file MT6575...emmc.txt
press the download button
plug in phone to usb
put battery in phone
watch the blinkinlights for a few seconds, wait for the big green O
then I disconnect phone and ensure power down.
install SDK
power up phone and plug in
test adb (adb shell)
kill adb server
download and install superoneclick
download extra superoneclick exploits
launch superoneclick
click the big root button.
Test (you can use something like rom manager)
Now people should be able to try to install various CWMs.
I haven't gotten that far yet.
Click to expand...
Click to collapse
Thanks for the steps though the problems are still coming thick and fast, I have a new U8812D from China, no China unicom splashscreen but lots of 'bloatware' still. I've been trying for days to root this thing and nothing's working.
I'm pretty sure I need root access becasue the phone is currently preventing me from adding my Gmail account and using the google play market and apps, other bits and pieces like assigning incoming call number to a contact are supposedly fixed by getting the google thing right. The phone is good but I'm missing alot of functionality.
If the above description sounds like rooting is not the solution, please let me know and point me to the right forum, if rooting is the obviously the only way out, I'm hoping to clarify a few step in the above walkthrough to help me and others.
1. I cant install the mt6575 MediaTek drivers, installing directly gives error 'driver cannot be installed this way' there is no COM-LPT port in my device manager to attach it to as a manually locate driver, I can add a COM port with add remove hardware but I have Code 10 error, device cannot start and doesnt seem to accept the mt6575 driver as an update even when forced to it with locate new driver, apparently this is no problem from other forums, still bugging me. Maybe I havent the right files? how do i get COM-LPT ports to show up properly?
2. when 'install m6575 drivers ... reboot' is the phone plugged in? to what device do we install the drivers or should it be automatic?
3. launch flash tool, i have located two versions of the MT6575...emmc.txt file, one delivers error, block count fail and has no files paths for the item in the main table, the other refuses to open, giving error, incorrect scatter file format. The latter has considerably more data in it when read in notepad.
4. Becasue of these errors, SP flash tool does not download to phone. all subsequent steps fail.
Assuming the initial flashing steps are successful, I must to use SuperOneClick to root the phone, where do I find the extra exploits needed? or are tehy automoatically sourced by SOC? Succeeding the root access step, I assume i can freeze the apps causing problems to my google sign in or delete them. Or could I please be directed to the ATTPlain rom mentionned by JohnnyParanoia in 'Almost All Huawei Stock Roms (Firmware) - Updated 28/06/12' board.
Since so many of the resource files I've trawled through are bung, anyone who can point me to reliable/tested files known to work with the U8812d I'd greatly appreciate in on top of the great appreciation I already have for your patience with a Noob. I located the 14Mbit .rar file mentioned above but not all parts worked, had to dl the different programs individually and some files had to hunt down form fileshare sites.
Lastly, i am using an HP laptop, Windows 7 64-bit, Thanks in advance.
Michael

How to Root and upgrade from ice cream sandwich to jelly bean??

Dear all,
I received an Asus Transformer Tf101 for Christmas, 16gb internal RAM,
OS 4.0.3 (ice cream). Can someone please guide me how to enable root and upgrade the os?
I tried to rooted with Sparkyroot but, kept getting " exploit not found". Please help!
Sent from my Transformer TF101 using xda app-developers app
Check to make sure the rooting method works with your device. Have you checked out the sticky threads here about it ? I remember that I tried three different ways of rooting (all from here) before it worked - I think it was a PC driver issue and a lack of support for one.
After that, you will need to install a custom recovery in order to flash from. I really like TWRP, and was advised to download "Goomanager" from the Play Store - from there you can go to the menu dots in the upper right and choose "Install OpenRecoveryScript" and it will install it. I also like the "Reboot2Recovery" app, although it's not as useful on a custom ROM that includes the feature, but is easier than holding down buttons just right for that first time.
After that, you can flash a ROM via that custom recovery you installed (on TWRP it is very user-friendly and very obvious what you need to do as long as you know what you need to "wipe" beforehand - all you need is to use the "Install" button and thereafter).
ROM+Kernel(optional)+GAPPS(Google proprietary apps) . You need to wipe both caches, /system and internal data. You could use Titanium Backup prior to this to backup apps and of course back up data to an external source. A Kernel is sort of an underlayer of the "OS" that works on a low level with the hardware. You can read about some of the available ones in the Development section and see why people are using them, what possible benefits they get, et cetera.
arabic support
do custom roms support foreign languages and fonts, i use to visit arabic web sites and arabic tweets, do CM10, AOSP or Teom eos support such fonts
Pennycake said:
Check to make sure the rooting method works with your device. Have you checked out the sticky threads here about it ? I remember that I tried three different ways of rooting (all from here) before it worked - I think it was a PC driver issue and a lack of support for one.
After that, you will need to install a custom recovery in order to flash from. I really like TWRP, and was advised to download "Goomanager" from the Play Store - from there you can go to the menu dots in the upper right and choose "Install OpenRecoveryScript" and it will install it. I also like the "Reboot2Recovery" app, although it's not as useful on a custom ROM that includes the feature, but is easier than holding down buttons just right for that first time.
After that, you can flash a ROM via that custom recovery you installed (on TWRP it is very user-friendly and very obvious what you need to do as long as you know what you need to "wipe" beforehand - all you need is to use the "Install" button and thereafter).
ROM+Kernel(optional)+GAPPS(Google proprietary apps) . You need to wipe both caches, /system and internal data. You could use Titanium Backup prior to this to backup apps and of course back up data to an external source. A Kernel is sort of an underlayer of the "OS" that works on a low level with the hardware. You can read about some of the available ones in the Development section and see why people are using them, what possible benefits they get, et cetera.
Click to expand...
Click to collapse
You should be fine with foreign languages as the custom rom is generally built on what Android uses, so if you can do it on stock than you should be fine on custom.
I use a different recovery than the above post, but if you follow his steps then you should be fine. You don't NEED a custom kernel to run JB per say, but it does give you a bit more power if you want to get into overclocking etc. Also, I try to stress, once you have custom recovery and are ready to flash whatever rom you chose, wipe everything. My first and only real panic was a bootloop from not wiping everything.
Like somebody mentioned above, make sure your device is compatible with each tool. Look at your serial number on the bottom of the tablet next to the usb port. Should see B60blahblah or B70blahblah, or maybe something higher (if it's newer).
I use a nice tool put together by whitekidney called EasyFlasher. It's an all in one package where you can root, install custom recovery, and install new firmware. Check this thread. It works very well for me, and is super easy.
whitekidney says:
Works for:
ANY TF101:
SBK1 (B10-B70)
SBK2 (B70,B80,B90++)
Some B70 models are SBK1, some newer B70 are SBK2, if you don't know which one you have, try both!
Click to expand...
Click to collapse
It's real easy to use. Put your tablet into apx mode by holding the power button and the volume up button. The screen will look like it's off but if you plug it into your Windows computer, you should hear the sound when a device is plugged it. Then it'll try to install the drivers for an apx device, or some MTP drivers, I believe. If they fail to install, download PDAnet and install it. This will correctly install your drivers. There's also another method of getting your drivers to install correctly. Here's a universal driver package that 1wayjonny put together. To clarify, only use PDAnet or the universal driver package if your drivers didn't install correctly when you plugged your transformer (which should be in apx mode) into your computer.
Now you can use EasyFlasher to install a custom recovery. I left it on the very first option, (a touch recovery, so you don't have to use your buttons to change your selection). During this process, EasyFlasher should first open up a command prompt (it might pop up behind your current programs running so you won't see it until you minimize everything except for EasyFlasher). The cmd prompt will ask you to overwrite some files on your device, just type a for "always" and let it do it's thing. It's really running NVflash which you should also get familiar with too.
After you have a custom recovery installed, flash your ROM of choice. Here's a nice JB 4.1 that I've tried out. Download that file, put it on a micro sd card, pop it in your transformer, and reboot into recovery by holding volume down and the power button. When it reboots, press volume up to enter your new custom recovery (like it should say on the screen). If you installed the same recovery that I recommended above (hopefully these are the correct steps, as I don't have my device in front of me), click on flash .zip, then click on from sd card. You should see the zip that you transferred from your computer, click on it, and it should install.
Once that's finished, reboot your transformer, let it load the new rom, either set it up or skip all the junk in the beginning. Once you're on the main home screen, remove your micro sd card and transfer the superuser zip that you can find inside the tools folder in EasyFlasher's directory (on your computer) to your sd card. Reboot into recovery, and now flash that super user zip the same way you flashed the rom.
Now you have a brand new, 4.1.2 JB rooted device!
Quick question, do i need to connect my asus eee transformer pad tf101 to my windows xp pc to root it? Or can i used my ibook g3. The reason i ask is because i keep getting an error about MTP error. I have search everywhere for this error and i cant find a solution.
Sent from my Transformer TF101 using xda app-developers app
jbusti75 said:
Quick question, do i need to connect my asus eee transformer pad tf101 to my windows xp pc to root it? Or can i used my ibook g3. The reason i ask is because i keep getting an error about MTP error. I have search everywhere for this error and i cant find a solution.
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
I am sure it can be done, but most of the tools (like EasyFlasher) use Windoze.
Even if you are getting an MTP error, it should not matter as you will be using the APX device. Just make sure you have the APX driver and update the unknown device that appears after you boot to APX mode.

[Completed] invalid OTA package missing scatter when trying to flash a zip file

Hi,
First of all, I am new to the android community and I hope that you will understand that I am writing as a noob.
I'm having an issue with my Chinese smartphone POMP W88A. It was a brand that was making smartphones, but it seems they have stopped producing phones. The phone is running on JB 4.2.2. It is running on MTK6589 processor. Kernel version is 3.4.5. Screen resolution is qHD (960x540). This phone seems like a Galaxy S4 clone. It has touchwiz installed, or I assume that it is touchwiz, even though it wont support the Accuweather S4 widget and other Samsung apps. What I was trying to do - I was going to install the Touchwiz launcher and the Accuweather widget from this link http://forum.xda-developers.com/showthread.php?t=2259228
It seems that it supports a large number of devices. However, when I rebooted into recovery and tryed to install the zips, I got an error message: Installation aborted. I googled a bit and found that some recoveries demand the zip files to be signed. I signed the zip files, rebooted again into recovery, and this time, the installation started, the progress bar started filling and suddenly it aborts the installation with this error message: "Invalid OTA package missing scatter". I tryed to google how to fix that problem, but I am unable to find a solution. There are some topics on this matter regarding the flashing of ROMs, but I just wanted to flash the launcher and the widget. I also found a topic saying that it might be because the Recovery demands Busybox to be installed, so I also installed Busybox, but the problem is still there. I also tried installing other recoveries via Mobileuncle Tools, but none of them worked, so I swithched back to the factory one, which is called Android system recovery 3e. Anyone have any clue how I can fix this? If there is a way to install zips without rebooting into recovery, I could try that, but I dont know if that is possible.
Here's the link for my phones ROM, maybe it could help you out to understand my issue:
http://www.needrom.com/download/pomp-w88a/
Thanks in advance. I would appreciate anyone's help.
Mirsaneli said:
Hi,
First of all, I am new to the android community and I hope that you will understand that I am writing as a noob.
I'm having an issue with my Chinese smartphone POMP W88A. It was a brand that was making smartphones, but it seems they have stopped producing phones. The phone is running on JB 4.2.2. It is running on MTK6589 processor. Kernel version is 3.4.5. Screen resolution is qHD (960x540). This phone seems like a Galaxy S4 clone. It has touchwiz installed, or I assume that it is touchwiz, even though it wont support the Accuweather S4 widget and other Samsung apps. What I was trying to do - I was going to install the Touchwiz launcher and the Accuweather widget from this link http://forum.xda-developers.com/showthread.php?t=2259228
It seems that it supports a large number of devices. However, when I rebooted into recovery and tryed to install the zips, I got an error message: Installation aborted. I googled a bit and found that some recoveries demand the zip files to be signed. I signed the zip files, rebooted again into recovery, and this time, the installation started, the progress bar started filling and suddenly it aborts the installation with this error message: "Invalid OTA package missing scatter". I tryed to google how to fix that problem, but I am unable to find a solution. There are some topics on this matter regarding the flashing of ROMs, but I just wanted to flash the launcher and the widget. I also found a topic saying that it might be because the Recovery demands Busybox to be installed, so I also installed Busybox, but the problem is still there. I also tried installing other recoveries via Mobileuncle Tools, but none of them worked, so I swithched back to the factory one, which is called Android system recovery 3e. Anyone have any clue how I can fix this? If there is a way to install zips without rebooting into recovery, I could try that, but I dont know if that is possible.
Here's the link for my phones ROM, maybe it could help you out to understand my issue:
http://www.needrom.com/download/pomp-w88a/
Thanks in advance. I would appreciate anyone's help.
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
About your problem, Chinese copies are not the best choice....
The error which appear to you it's cause also for the fact that you need a custom recovery for it like TWRP or CWM.
If you are able to get root access on your phone you could simply decompress the flashable zip and then push to system the files to their respective folders.
Other ways i couldn't find.
But for futher assistance i suggest you to head over here: Android Q&A, Help & Troubleshooting
nilac said:
Hi and thank you for using XDA Assist
About your problem, Chinese copies are not the best choice....
The error which appear to you it's cause also for the fact that you need a custom recovery for it like TWRP or CWM.
If you are able to get root access on your phone you could simply decompress the flashable zip and then push to system the files to their respective folders.
Other ways i couldn't find.
But for futher assistance i suggest you to head over here: Android Q&A, Help & Troubleshooting
Click to expand...
Click to collapse
Yeah, I know they are not very stable. I was wondering something: when I reboot into recovery, I dont have an option called Install zip from SD card, like many other recoveries I saw on Youtube have. I only have Apply update from SD Card, Apply update from Cache and Wipe partition data. Maybe that option "Apply update from SD card" that I was trying is ment for installation of ROMs and flashing updates. Im just guessing... So, how could I install CWM? I already checked the TWRP website, but ofc I couldn't find my device on their list. CWM, however, I don't know how it works. About pushing the apks into system/app - I already tried pushing various launchers into system/app and changing permissions, but none of them worked. Last one bricked my phone, so I reflashed the ROM via SP flash tool. Now its working smoothly, but on the other hand, I payed this phone pretty cheap, and I would love to customize it and learn something new about customizing

[ROOT/RECOVERY]Working method for sm-t237p Sprint Variant 7" running 5.1.1

OK, after messing around for a bit, i was able to get root, and custom recovery working, and its actually pretty simple...
1. - Update to 5.1.1 via ota,
2. - Download Philz (CWM touch) Recovery and Beta SuperSU 2.64 (System-Less Root) (Pretty sure its in post #3).
3. - Copy the SuperSu .zip file to your sdcard on the Galaxy tab.
4. - Make sure you have the proper samsung drivers for download mode, and place you tablet in download mode by holding Vol-/Home/Power then pressing vol+ to continue.
5. - Connect you PC to the tablet using a suitable micro usb cable and use odin (I use version 3.10.7) and make sure you see you device under ID:COM.
6. - Click the AP button (PDA button in older versions), and browse to where you have the Philz recovery .tar file, and also select the options tab and deselect the auto reboot option.
7. - Click Start, and once you see pass, you can unplug your device from the computer, but do not just reboot the tablet normally just yet.
8. - Reboot the device to recovery by holding Vol+/Home/Power, and if all went well, you should be in philz recovery.
9. - Do a full system backup (warning you will need at least 4GB of storage available).
10. - Once backup completes, install zip from sdcard, and navigate to where you put the SuperSU 2.64 zip file, and flash it.
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.64 file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk and PROFIT!!!
If you have any questions, I'll try and fill in, i know that some of this write up is written with the expectation that you have knowledge of what you are doing, as i didn't explain in detail some actions necessary, but if you are rooting, and flashing recoveries, i assume you know what you are doing somewhat... With that being said i take no responsibility for any damage you may cause your device attempting this process, and i will not be replacing anyones device if you brick you tablet, your tablet catches on fire, or if your tablet turns into the devil and steals your soul. You are on your own...
But realistically this process was pretty easy, and i figured it all out just today, so i'm pretty sure you can do the same.
This is only a temporary solution for root, until a full kernel can be released, and we can fully root system, but for apps like titanium, es file explorer, and such (I haven't' tried debloating, you are on your own with that), this works... Once a custom kernel is developed (looks like @moonbutt74 is working that angle btw... ) you will definitely be able to debloat, and flash whatever you might want granted it is for this device...
EDIT** I forgot to mention this will trigger the KNOX counter, so if you don't care then continue as you would, pretty sure if you are looking to root, you don't care about the KNOX counter, and if you do, then maybe you should be looking into somehow writing a stock kernel that can be customized without triggering KNOX, slightly more advanced then what we are doing here... **
EDIT** Please give credit to the guy who "found it first" and should have done the write up but didn't**
@K94U
http://forum.xda-developers.com/tab-4/help/root-sm-t237p-5-1-1-t3211541/page2
http://forum.xda-developers.com/tab-4/general/to-root-samsung-galaxy-tab-4-t3264281/page2
I was going to write some very insulting message, but i don't want to fill this thread with stupid nonsense, as it is completely obvious that you have no clue what you are talking about... Just a few areas where i'v helped...
http://forum.xda-developers.com/showpost.php?p=38886073
http://forum.xda-developers.com/showpost.php?p=26608802
http://forum.xda-developers.com/showthread.php?p=34381433#post34381433
Yes that is my phone in post 3, as i was the first outside of the team to have a rooted LG optimus G, thanks to TeamCodefire, shellnut2, JCase, AutoPrime, thecubed, and many more that contributed to the lg root evolution. If you have any questions about my integrity, you can ask any of them...
I cleaned the offensive posts and the user was infracted. At the OP, thanks for managing this appropriately and not escalating it to a flame war.
Back on topic please.
These steps are NOT needed... Once you complete step 10 and reboot SuperSU is installed and accessible...
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.64 file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk and PROFIT!!!
This is only a temporary solution for root... Why?
And, the Kingroot and Super Sume method works sometimes to get root without tripping KNOX! This info I also posted in another thread...
This recovery/root method will work for mostly ALL Samsung and Nexus devices that have a working recovery... Thanks to Chainfire for his hard work!
K94U said:
These steps are NOT needed... Once you complete step 10 and reboot SuperSU is installed and accessible...
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.64 file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk and PROFIT!!!
This is only a temporary solution for root... Why?
And, the Kingroot and Super Sume method works sometimes to get root without tripping KNOX! This info I also posted in another thread...
This recovery/root method will work for mostly ALL Samsung and Nexus devices that have a working recovery... Thanks to Chainfire for his hard work!
Click to expand...
Click to collapse
Temporary solution is in the meaning of not fully rooted... This method is systemless, and if you want to make full init.d edits, i would not recommend using a systemless root option, as its kinda like a sudo root, for those that use linux, they will understand what i'm talking about. Yes you can allow root access to apps the request it, but as for full system modifications like the sound mixer, and init.d edits, i don't think i would go there, also not really sure if this will work with debloating, I'm not exactly sure about on samsung how it acts when you remove "system" apps (more so apps installed by default by samsung), I do know that one of the quickest ways to brick a lg is to remove system apps, and if you don't have an unlocked bootloader, as well as custom kernel, during boot, you get a kernel panic if system apps are removed, and in some cases has rendered the device unusable, (nothing an insurance claim couldn't fix tho... lol). Oh, and for the final steps, i actually did have to do them, I had no superuser app in my apps drawer, I attempted downloading from the playstore, and it was the wrong version SuperSU, and kept telling me i needed to update my binary. Then did steps 11-13, and all was nice in the world again, and no more nag about updating binaries, as well as it is the correct apk for the su binary that is flashed in step 10.
fiddy619 said:
Temporary solution is in the meaning of not fully rooted... This method is systemless, and if you want to make full init.d edits, i would not recommend using a systemless root option, as its kinda like a sudo root, for those that use linux, they will understand what i'm talking about. Yes you can allow root access to apps the request it, but as for full system modifications like the sound mixer, and init.d edits, i don't think i would go there, also not really sure if this will work with debloating, I'm not exactly sure about on samsung how it acts when you remove "system" apps (more so apps installed by default by samsung), I do know that one of the quickest ways to brick a lg is to remove system apps, and if you don't have an unlocked bootloader, as well as custom kernel, during boot, you get a kernel panic if system apps are removed, and in some cases has rendered the device unusable, (nothing an insurance claim couldn't fix tho... lol). Oh, and for the final steps, i actually did have to do them, I had no superuser app in my apps drawer, I attempted downloading from the playstore, and it was the wrong version SuperSU, and kept telling me i needed to update my binary. Then did steps 11-13, and all was nice in the world again, and no more nag about updating binaries, as well as it is the correct apk for the su binary that is flashed in step 10.
Click to expand...
Click to collapse
Im currently on 4.2.2 with rooted philz recovery.
How can i get to 5.x? If i use OTA I imagine id loose root.
this trick works ...my tab 4 never looked this better
HELP!!!
Having an issue with my sm-237p . Download mode is not allowing me to flash anything via odin. I am trying to root my tab. Recoveries nor firmware wil flash. it starts but never ,akes progress. please help
A samson sm-T237P is sheeped to Nigeria,the problem is that you cannot make call with it because it is not connected with the network here.
Is there an updated way to do this root? I can't get the files I need to root like this
fiddy619 said:
OK, after messing around for a bit, i was able to get root, and custom recovery working, and its actually pretty simple...
1. - Update to 5.1.1 via ota,
2. - Download Philz (CWM touch) Recovery and Beta SuperSU 2.64 (System-Less Root) (Pretty sure its in post #3).
3. - Copy the SuperSu .zip file to your sdcard on the Galaxy tab.
4. - Make sure you have the proper samsung drivers for download mode, and place you tablet in download mode by holding Vol-/Home/Power then pressing vol+ to continue.
5. - Connect you PC to the tablet using a suitable micro usb cable and use odin (I use version 3.10.7) and make sure you see you device under ID:COM.
6. - Click the AP button (PDA button in older versions), and browse to where you have the Philz recovery .tar file, and also select the options tab and deselect the auto reboot option.
7. - Click Start, and once you see pass, you can unplug your device from the computer, but do not just reboot the tablet normally just yet.
8. - Reboot the device to recovery by holding Vol+/Home/Power, and if all went well, you should be in philz recovery.
9. - Do a full system backup (warning you will need at least 4GB of storage available).
10. - Once backup completes, install zip from sdcard, and navigate to where you put the SuperSU 2.64 zip file, and flash it.
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.64 file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk and PROFIT!!!
If you have any questions, I'll try and fill in, i know that some of this write up is written with the expectation that you have knowledge of what you are doing, as i didn't explain in detail some actions necessary, but if you are rooting, and flashing recoveries, i assume you know what you are doing somewhat... With that being said i take no responsibility for any damage you may cause your device attempting this process, and i will not be replacing anyones device if you brick you tablet, your tablet catches on fire, or if your tablet turns into the devil and steals your soul. You are on your own...
But realistically this process was pretty easy, and i figured it all out just today, so i'm pretty sure you can do the same.
This is only a temporary solution for root, until a full kernel can be released, and we can fully root system, but for apps like titanium, es file explorer, and such (I haven't' tried debloating, you are on your own with that), this works... Once a custom kernel is developed (looks like @moonbutt74 is working that angle btw... ) you will definitely be able to debloat, and flash whatever you might want granted it is for this device...
EDIT** I forgot to mention this will trigger the KNOX counter, so if you don't care then continue as you would, pretty sure if you are looking to root, you don't care about the KNOX counter, and if you do, then maybe you should be looking into somehow writing a stock kernel that can be customized without triggering KNOX, slightly more advanced then what we are doing here... **
EDIT** Please give credit to the guy who "found it first" and should have done the write up but didn't**
@K94U
http://forum.xda-developers.com/tab-4/help/root-sm-t237p-5-1-1-t3211541/page2
http://forum.xda-developers.com/tab-4/general/to-root-samsung-galaxy-tab-4-t3264281/page2
Click to expand...
Click to collapse
Mjme34 said:
Is there an updated way to do this root? I can't get the files I need to root like this
Click to expand...
Click to collapse
Here's the magic: mega(dot)nz/#F!ZkARSbRI!SV3kQ6jmsi9eGwHoRKPfew
(sry first post.. they have rules against posting web links directly.. replace (dot) with . and you should have your recovery file)
had to do a bit of digging myself. The other files should be easy to find via Google.
fiddy619 said:
OK, after messing around for a bit, i was able to get root, and custom recovery working, and its actually pretty simple...
1. - Update to 5.1.1 via ota,
2. - Download Philz (CWM touch) Recovery and Beta SuperSU 2.64 (System-Less Root) (Pretty sure its in post #3).
3. - Copy the SuperSu .zip file to your sdcard on the Galaxy tab.
4. - Make sure you have the proper samsung drivers for download mode, and place you tablet in download mode by holding Vol-/Home/Power then pressing vol+ to continue.
5. - Connect you PC to the tablet using a suitable micro usb cable and use odin (I use version 3.10.7) and make sure you see you device under ID:COM.
6. - Click the AP button (PDA button in older versions), and browse to where you have the Philz recovery .tar file, and also select the options tab and deselect the auto reboot option.
7. - Click Start, and once you see pass, you can unplug your device from the computer, but do not just reboot the tablet normally just yet.
8. - Reboot the device to recovery by holding Vol+/Home/Power, and if all went well, you should be in philz recovery.
9. - Do a full system backup (warning you will need at least 4GB of storage available).
10. - Once backup completes, install zip from sdcard, and navigate to where you put the SuperSU 2.64 zip file, and flash it.
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.64 file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk and PROFIT!!!
If you have any questions, I'll try and fill in, i know that some of this write up is written with the expectation that you have knowledge of what you are doing, as i didn't explain in detail some actions necessary, but if you are rooting, and flashing recoveries, i assume you know what you are doing somewhat... With that being said i take no responsibility for any damage you may cause your device attempting this process, and i will not be replacing anyones device if you brick you tablet, your tablet catches on fire, or if your tablet turns into the devil and steals your soul. You are on your own...
But realistically this process was pretty easy, and i figured it all out just today, so i'm pretty sure you can do the same.
This is only a temporary solution for root, until a full kernel can be released, and we can fully root system, but for apps like titanium, es file explorer, and such (I haven't' tried debloating, you are on your own with that), this works... Once a custom kernel is developed (looks like @moonbutt74 is working that angle btw... ) you will definitely be able to debloat, and flash whatever you might want granted it is for this device...
EDIT** I forgot to mention this will trigger the KNOX counter, so if you don't care then continue as you would, pretty sure if you are looking to root, you don't care about the KNOX counter, and if you do, then maybe you should be looking into somehow writing a stock kernel that can be customized without triggering KNOX, slightly more advanced then what we are doing here... **
EDIT** Please give credit to the guy who "found it first" and should have done the write up but didn't**
@K94U
http://forum.xda-developers.com/tab-4/help/root-sm-t237p-5-1-1-t3211541/page2
http://forum.xda-developers.com/tab-4/general/to-root-samsung-galaxy-tab-4-t3264281/page2
Click to expand...
Click to collapse
Can you fix the link to the recovery says 404 not found
g7755725 said:
Can you fix the link to the recovery says 404 not found
Click to expand...
Click to collapse
Just Read the posts before yours, the link is right there.
There's a reason posts are added and not just replaced with new ones. This is only a 2 paged thread, not hard at all to read it all.
g7755725 said:
Can you fix the link to the recovery says 404 not found
Click to expand...
Click to collapse
Updated, but like bodyshop said... look up. No offense tho...
Thanks for this, however I can't get wifi to turn on. I saw mention in another thread about deleting wpa_supplicant.conf and using ODIN to upgrade to PF1 (could only find PH4 but it fails), but neither worked. Does anyone know of a fix?
thank you 403sc softbank
thank you for solution 403sc softbank
i find tools 7 hour
thank you again

Categories

Resources