Hello,
I have a Allview Speed City tablet, and after i installed root on it, i changed the dpi using an app..
(root thanks to mad_ady, root availible at http://forum.xda-developers.com/showthread.php?p=40740061#post40740061 )
After this, the tablet is stuck in a boot loop.
I tried to do a factory reset from recovery mode, but this didn't solved the problem.
(the tablet has only 2 buttons, power and home. The recovery can be accessed pressing and holding both buttons until the recovery boot).
I located the file where the dpi is changing, /system/build.prop , and tried to flash another file from Onda 701 ROM (a very similar tablet). I didn't managed to find the original file. Anyway, the flashing didn't succeeded, "instalation aborted" appeared on the screen.
I found on some forum a flashable zip with build.prop from another device, and i replaced the build.prop file with the one from Onda ROM, signed it with a tiny program and still fails.
What options do i have to replace/edit the build.prop file? Before bricking, the ADB was not turned on on the tablet, and i read that i cannot use the SDK (anyway don't know how to use it). I contacted Allview and they don't want to give me the ROM from the tablet. And so, i call anybody that can give me a backed up rom from the tablet, anyone who have the knowledge about AD ROMS and are willing to help me..
Thanks folks!
I installed ADB on my pc and tried to pull the build.system file from /system on tablet, but i get error:closed.. I tried to run this command with tablet in recovery/ apply update from ADB.. Why do i get this error? the device cannot recieve other commands than adb sideload?
Thanks..
this worked for me for full reset
crististan said:
I installed ADB on my pc and tried to pull the build.system file from /system on tablet, but i get error:closed.. I tried to run this command with tablet in recovery/ apply update from ADB.. Why do i get this error? the device cannot recieve other commands than adb sideload?
Thanks..
Click to expand...
Click to collapse
this has been done with the allview speed city
I had a simular problem...
here my solution, hold on and home button at the same time until the screen gets back
wait until you get the boot screen...
use both, 1. erase card and 2. media options...
then to be save I choosed the other option say something like for factory reset.
the I used the apply update from ADB...
the tablet shows the same screen for 5 or 6 minutes
after it booted normaly, but I still had some problems
and I used a needle for a reset...
after that the tablet worked fine
the only thing what I dont understand is why its still root
Thank you for this tutorial, but i solved my problem with warranty. Even so, i erased all cache, factory reset from recovery but still i had no access to system files, and factory reset didn't changed the build.prop (system settings) to defaults.
It's normal. build.prop is part of /system (and the su binary is installed under /system as well), and any changes you make to /system files are permanent until you flash a different firmware.
Related
I rooted my Galaxy Pocket lately and installed LCD modder just to try changing the dpi settings. i changed the stock 120 dpi to 160 and clicked save. the phone froze and i had to pull of the battery. after i restart all i get is a boot loop. i get 3 things (1) s5300 logo (2) animated samsung logo (3) flashing samsung logo which appears just before the lock screen appears ( 1 and 2 vibrations during this) and then it loops all over again. as i understand the change i dpi is not supported for my device and it is not loading into the home screen. the solution seems to be editing the build.prop file to reassign the stock dpi value. but to access the file i have to get into adb mode and have the device available in the list. but since debugging mode was not selected before i essentially soft bricked my phone i am not able to access my device in adb mode. i am able to get into recovery mode tho.any way to edit the build.prop file from this situation?? help is much appreciated.....i am travelling now and my phone is unusable......thanks a ton..
If you can get to download mode, than you can reflash to stock rom again..
Sent from my GT-S5300 using Tapatalk 2
thanks for the idea..i am able to get into download mode....im sure i can reflash my phone with a new firmware to get it up and going....but i would loose all my contacts and data on the phone, which unfortunately i hadnt backed up since i wasnt expecting this situation to arise. (my badd!!!!). as far as i know the only thing that prevents my phone from booting up properly is the "LCD density property line" in build.prop. Is there anyway i can just edit it back to my stock setting (dpi 120). ????
I had come across the term CWM which is said to be an alternative recovery option. does it mean i can get into CWM recovery mode from switched off state with button combos just like i get into android stock recovery menu??? and if dats possible, can i apply an update.zip from my memory card that would change this dpi setting in the build.prop some how?? how can i get clockworkmod into my system without flashing the firmware and erasing the data (without flashing)??? thanks......
or can i just change/flash the bootloader (which i understand contains all the system files necessary to bootup the phone) using ODIN flash. if so...can i get the stock bootloader from an s5300 user like u?? I know flashing would be the easiest option now..but i just want to go to all extremes to just keep my data if possible in anyway. if there is anyway to have ADB working without debugging mode on or any way to activate debugging mode from the recovery menu or download menu?
help much appreciated
Well, in s5300 we use cwm that had aroma file manager that can run in recovery mode.like file explorer.that might solve you problem to edit build prop.
Sent from my GT-S5300 using Tapatalk 2
bayustev said:
Well, in s5300 we use cwm that had aroma file manager that can run in recovery mode.like file explorer.that might solve you problem to edit build prop.
Sent from my GT-S5300 using Tapatalk 2
Click to expand...
Click to collapse
thanks for the insight...Could you just give me a small"how-to" on this idea???
how do i install cwm with aroma file manager?? all the videos i saw on youtube shows the installation after its being copied into internal storage when the phone is on and then getting into recovery mode to install it, so hw do i get it into phone memory or may be into SD card if there is a way to mount it in recovery mode
appreciate your speedy reply man...
Cwm vM00v3f. Flash with odin (if you don't had custom recovery mode). Than v00kernelv1.10. Then get into recovery mode. In there you see aroma manager inside recovery mode. Click it .there you can explore file folder on your device.search the file you want to edit..for cf root link you type in search box ..
send from p1010 kmicic rom tapatalk 2
galaxy pocket lcd density problem
I have the same problem but I have open usb debug
jkanth7 said:
thanks for the idea..i am able to get into download mode....im sure i can reflash my phone with a new firmware to get it up and going....but i would loose all my contacts and data on the phone, which unfortunately i hadnt backed up since i wasnt expecting this situation to arise. (my badd!!!!). as far as i know the only thing that prevents my phone from booting up properly is the "LCD density property line" in build.prop. Is there anyway i can just edit it back to my stock setting (dpi 120). ????
I had come across the term CWM which is said to be an alternative recovery option. does it mean i can get into CWM recovery mode from switched off state with button combos just like i get into android stock recovery menu??? and if dats possible, can i apply an update.zip from my memory card that would change this dpi setting in the build.prop some how?? how can i get clockworkmod into my system without flashing the firmware and erasing the data (without flashing)??? thanks......
or can i just change/flash the bootloader (which i understand contains all the system files necessary to bootup the phone) using ODIN flash. if so...can i get the stock bootloader from an s5300 user like u?? I know flashing would be the easiest option now..but i just want to go to all extremes to just keep my data if possible in anyway. if there is anyway to have ADB working without debugging mode on or any way to activate debugging mode from the recovery menu or download menu?
help much appreciated
Click to expand...
Click to collapse
flash Phil touch or Cwm through download mode and then you can use adb tools. Open up cmd cd /d C:\where you saved your SDK (mini-sdk is quick to download just search mini-sdk on Google and click the first one) now adb pull /system/build.prop it should be where your sdk is, then edit with notepad ++. Once you've done this do adb push build.prop /system. You can flash recovery without wiping any data.
I tried to root my me302kl by following the first post described in this thread, but it seems I've bricked my tablet
http://forum.xda-developers.com/showthread.php?t=2601837
I have the LTE version, unlocked the bootloader using the apk from Asus, and followed the fastboot method in the first post, and now I'm stuck at the Asus logo on startup. I'm trying to factory reset by using the update download from the Asus website, but when i try
fastboot erase cache
fastboot erase system
fastboot flash update US_ME302C-V4.7.3-0-ota-user.zip
it fails with this:
writing 'update'...
FAILED (remote: partition table doesn't exist)
Then I tried following perpe's advice but both methods did not work
Download the update zip for your device and sku from ASUS. Unpack it once, there should be a second zip, try to flash it with
fastboot update name-of-your.zip
if this doesn't wotk, then copy the update zip to an external sd card. Your sd card should be formated in far32. Place the card into the tablets sd card. Press Volume UP + Power to boot it into the bootloader, it should flash it automatically, if not look if yor bootloader has a menu entry "sd download..." select it with the volume keys and power.
Click to expand...
Click to collapse
When booting into recovery mode, I get the dead android robot icon, regardless of whether the .zip file is on the SD card or not. I've also tried making a system.img file out of the system folder from the extracted zip file and flashing that with fastboot flash system system.img and fastboot flash boot boot.img, but that didn't work either.
Any kind soul have advice on how to make use of the official Asus OTA .zip file, or perhaps be able to supply some .img backups for me to make use of?
EDIT
Found out that to get the recovery menu to show up, you have to hold the power button and press volume up. I thought that the menu would show up automatically so I got confused. ADB sideloaded the Asus OTA .zip and everything is back to normal
Hello
How to flash oryginal soft on this tablet. Can you help with this ?
I tried SDK and wiped all system but now i cannot flash the system. How should i do it ?
I have firmware fros ASUS page and now what?
I tried fastboot flash update... but i have measege that unknown partition and cannot determinate image file name. What im doing wrong?
Thanks!
Lenino83 said:
Hello
How to flash oryginal soft on this tablet. Can you help with this ?
I tried SDK and wiped all system but now i cannot flash the system. How should i do it ?
I have firmware fros ASUS page and now what?
I tried fastboot flash update... but i have measege that unknown partition and cannot determinate image file name. What im doing wrong?
Thanks!
Click to expand...
Click to collapse
download the OTA zip from the asus website
unzip once, you should have another zip
power on the tablet while holding volume up to boot into recovery mode
after the android robot shows up, hold volume up and press the power button to get the recovery menu to show
install the zip using adb sideload
using adb sideload will differ depending on what OS you're using. you can google to find out more specific instructions for that because it's a little more work to get it for windows. for OSX if you have homebrew, you can just 'brew install android' and it will install all the android tools for you.
once you have adb installed, in the terminal type 'adb sideload pathname_of_zip.zip' and it will restore your device to factory settings
I had the same problem and your trick saved me from sending it back. I am not sure if i would have send it back as I have yet to brick something since I am playing with android back in the days of Viewsonic gtablet. We are stuck with 4.2.
Sent from my T0LTE using Tapatalk
help
tkuichooseyou said:
Found out that to get the recovery menu to show up, you have to hold the power button and press volume up. I thought that the menu would show up automatically so I got confused. ADB sideloaded the Asus OTA .zip and everything is back to normal
Click to expand...
Click to collapse
hello
got like the same problem.. dead robot, no boot, in recovery does not want to update from ota file.
Can u explain please how to ADB sideload ota.zip?
What I need, drivers and step by step?
I tried but I get no device in adb
Thank you:crying:
ionratiu2000 said:
hello
got like the same problem.. dead robot, no boot, in recovery does not want to update from ota file.
Can u explain please how to ADB sideload ota.zip?
What I need, drivers and step by step?
I tried but I get no device in adb
Thank you:crying:
Click to expand...
Click to collapse
You have to download adb or android sdk, or google how to install adb. Once you have installed the adb, hold the power button, and either Volume UP or down to put tablet into bootlfash recovery mode. Once you have it in recovery mode, push volume up or down to get into true recovery mode.
There you would see adb sideload.
Download US or WWW files from Asus website, and unzip the file into ADB directory or whatever path. then type adb sideload name of the file.
Please read the 1st post by OP on this thread twice or three times, and it tells you how to get your tablet back from brink.
back
rob_z11 said:
You have to download adb or android sdk, or google how to install adb. Once you have installed the adb, hold the power button, and either Volume UP or down to put tablet into bootlfash recovery mode. Once you have it in recovery mode, push volume up or down to get into true recovery mode.
There you would see adb sideload.
Download US or WWW files from Asus website, and unzip the file into ADB directory or whatever path. then type adb sideload name of the file.
Please read the 1st post by OP on this thread twice or three times, and it tells you how to get your tablet back from brink.
Click to expand...
Click to collapse
Got it. Done! the tablet is running again, but I encounter another issue
I have no permission to write internal sd.
I cant touch internal, some apps that require writing don't work (play store, camera, etc) I cant root, unlock or do anything that require w permissions.
Any way to fix that?
Or I have to wait for a CWM and rom image ?
ionratiu2000 said:
Got it. Done! the tablet is running again, but I encounter another issue
I have no permission to write internal sd.
I cant touch internal, some apps that require writing don't work (play store, camera, etc) I cant root, unlock or do anything that require w permissions.
Any way to fix that?
Or I have to wait for a CWM and rom image ?
Click to expand...
Click to collapse
You can download king's root or something which is a window app, and it does give your tablet root. I am not exactly sure about the name, but would let you know once I have access to my laptop.
Sent from my T0LTE using Tapatalk
ASUS MEMO PAD FHD10 ME302KL frozen logo screen
I have problem with my asus memo pad 10. It just shows asus logo startup screen and nothing more and it have no reaction with anything I do.
Please help!
I can't boot into recovery mode, but there is no problem to boot into fastboot mode!
Could anyone provide stock recovery file or link? Then I can flash recovery and do the adb sideload.
Thanks!!
Hi everyone, I have a problem. I recently got a Huawei y220 and rooted it and enabled USB debugging, tweaked the SystemUI.apk and it all went good, I had no problem rebooting. I also changed my bootscren with BootScreen from the Play Store.
But today, my phone got stucked in bootloop, and i know why, I changed the /system/fonts permissions to 666, and also when I was trying to change the default font (DroidSans.tttf and DroidSansBold.ttf) copied a font file, so in that folder there was some permissions changed and an extra font. I had to to do something so i locked my phone. When I returned a couple of minutes later the phone was like off, so i removed the battery and rebooted it. It got stucked on my bootscreen, and didn't showed me my ADW launcher.
I can't install CWM as there is no file for this model (because it's very new), I can't flash anything as far as I know. Tried downloading the official "upgrade" from Huawei, copied the file, but I can't seem to enter the "Software Upgrade Mode", (VOL UP + VOL DOWN + POWER KEY), I press those keys for about a minute and nothing happens.
I know my phone isn't fully bricked, for now, so, how can I change those file permissions through my PC or Linux?
I can enter the bootloader screen BTW.
I also tried AromaFM, but i get a signature error.
I've already wiped/factory reset and wiped cache.
Thanks for your time!
--
TheEdwardRC
I thought the way you update / restore the stock firmware was by the update.app method? The update should be in an archive and once you unpack it should be a folder named : dload with the update.app in it. That whole folder should go on the root of the SD card so it should read /sdcard/dload. Unless it is a different y220...
Otherwise, you're kinda screwed because unless you have adb access when it is bootlooping (rare), there won't be much to do. You won't have adb in recovery either since it is still stock.
I guess it is the normal y220. The problem is that I can't get into the Software Upgrade Mode. Also, my other choice was AromaFM but i don't know how to stop it to verify the signature verification. If i could do that, i could have root acces to the files. Or maybe could install a POSSIBLE backup that i found online...
Well, when i am in recovery the device is detected on windows, but ot mounted...
Thank you
My point was, according to the info that I found, you don't update that one via the Software Update mode, you do it via the method I was talking about with the update.app in the dload folder on the SD card.
Huawei Ascend Y220 U00
After installing a theme pack, my huawei Y220 has been stuck in bootloop. I found a toolkit on some forum, it requires my device mounted on a Computer, I got all necessary drivers, but the pc could not install my device. It shows the device on device manager on the PC but after 3sec it ejects. Pls I need help.
look here, this will help you unbrick your device
http://en.club.vmall.com/forum.php?mod=viewthread&tid=13433&highlight=unbrick+huawei
Tablet is a off brand: QPS m006F-2
Spec sheet says Allwinner A20 CPU, but when booting, the first splash screen shows a logo for a Allwinner A31S.
Device was running factory 4.2 ROM with unlocked bootloader. Rooting was a matter of just downloading a app off the market.
Edited the /system/build.prop file for something unrelated to rooting, By pull/push with ADB. ADB showed the whole file uploaded. Upon reboot, it would get stuck at the Android splash screen. Tried pulling the Build.prop file to remove the change, only to find the file is blank. Stupidly I didn't save a backup of the file. Tried all the wipe/restore options in the factory recovery manager, none made a difference.
Couldn't find a exact ROM for this device. Couldn't find anything in the internal disk when browsing the file system through the factory recovery manager. I tried pushing CWM .img to the device, but could not see it in the recovery manager. Next I tried a function labeled "load from adb" in the recovery manager. It instructed to execute "adb sideload <filename>" from adb. I used TWRP 2.6 (Onda v811) from here, referenced by this post. This executed fine, upon reboot, TWRP comes up fine, but no screen touches or volume button presses do anything. So it seems since TWRP replaced the factory recovery manager, I now have no avenue to load anything else on the device. The device also no longer shows up for ADB now that TWRP has been installed. So am I out of luck and this thing is bricked?
bump.
microwarz said:
Tablet is a off brand: QPS m006F-2
Spec sheet says Allwinner A20 CPU, but when booting, the first splash screen shows a logo for a Allwinner A31S.
Device was running factory 4.2 ROM with unlocked bootloader. Rooting was a matter of just downloading a app off the market.
Edited the /system/build.prop file for something unrelated to rooting, By pull/push with ADB. ADB showed the whole file uploaded. Upon reboot, it would get stuck at the Android splash screen. Tried pulling the Build.prop file to remove the change, only to find the file is blank. Stupidly I didn't save a backup of the file. Tried all the wipe/restore options in the factory recovery manager, none made a difference.
Couldn't find a exact ROM for this device. Couldn't find anything in the internal disk when browsing the file system through the factory recovery manager. I tried pushing CWM .img to the device, but could not see it in the recovery manager. Next I tried a function labeled "load from adb" in the recovery manager. It instructed to execute "adb sideload <filename>" from adb. I used TWRP 2.6 (Onda v811) from here, referenced by this post. This executed fine, upon reboot, TWRP comes up fine, but no screen touches or volume button presses do anything. So it seems since TWRP replaced the factory recovery manager, I now have no avenue to load anything else on the device. The device also no longer shows up for ADB now that TWRP has been installed. So am I out of luck and this thing is bricked?
Click to expand...
Click to collapse
if your device is not booting and shows only company logo then it is soft bricked
I decided to root my ME302C tablet to remove some bloatware using an app that required a rooted device. I had the latest firmware so I couldn't use any of the rooting guides online, but I tried Kingo Root, an automatic rooting PC program (all I had to do was enabled USB Debugging), and it worked, at least for one session (after a reboot, it appears to stop working).
After I removed the bloatware, I reset the tablet to its factory state without using the remove root option in Kingo SuperUser (not SuperSU) (I did not know that the option existed). I'm not sure if it would have made a difference if I had used that option, but after resetting, Android booted properly, but I had no lock screen, broken default browser, unresponsive on-screen home button, no notification area, and I lost some options that appeared when powering off (airplane mode and mute). I occasionally get "unfortunately *app* has stopped" errors, but it doesn't appear to affect anything. The tablet works fine otherwise.
I would really appreciate it if someone could direct me on how to restore the default firmware entirely. If I factory-reset, it just removes the apps and resets the settings without affecting the system (clears cache and user partitions), and this website confirms that: search for Isn't Factory Reset exactly the same as wiping /data and /cache? stackexchange. I can't link to it directly. Sorry.
I found a post about an unrelated problem while typing the title where somebody attempted to root using an unofficial firmware update and totally bricked their FHD 10. They ran these commands:
fastboot erase cache
fastboot erase system
fastboot flash update "updatename".zip
Suppose that instead of using the unofficial, rooted update.zip he used, I used an official one from this page (it contains links to updates for my tablet's firmware): search for me302c asus. I can't link to it directly. Sorry.
Would that work? I am assuming that a firmware update is a copy of the entire firmware.
If I could use an update, could you please let me know how to flash it exactly? I can boot into recovery mode, Droidboot Provision OS. It has an option to update the firmware, I believe, called "SD DOWNLOAD". If I place an update.zip file named ASUS_BUNDLE.zip on an external SD card and use the option, it'll look like it's updating (there are a few screens, I think they say "clearing cache" and something else, but nothing mentioned of the system partition) - however, it just acts as if it is a factory reset, taking me back to that state where things are borken.
SD Download doesn't look like it is doing something for every random ZIP you put on the SD card, because if I use a ZIP file that has, say, a picture of my cat enclosed, it will not do anything. I think that it does do something with the ASUS_BUNDLE.ZIP, but just not anything that solves my problem.
In Droidboot, if I plug a USB cable into the tablet and the other end into my PC, an icon will appear saying "USB connected". If I enable USB debugging in Android and connect the tablet to my PC in the Droidboot Provision OS recovery mode, should I run the commands then?
I realize that this is a mouthful and thank you for taking the time to read my post.
Did you solve this in the end?
Yes.
_MsG_ said:
Did you solve this in the end?
Click to expand...
Click to collapse
I used the method that I posted to fix the tablet.