Phone model : Huawei G610-U20
Hey guys, I'm new to this ADB stuff and root editing files.
What I did was try to run an nvidia shield game but since it wont launch I thought that it's probably my build.prop now allowing me to run it since some other guy made it run because he changed his build.prop. When i applied the changes and restarted the phone, I got stuck on bootloop, usb debugging is disabled, no CWM installed, I can't flash the update.app in my SD card through download mode, although I can get to recovery mode. ADB can't detect my device. Is there anyway to fix this problem maybe through flashing from a third-party app such as livesuite or something? Thanks in advance.
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.
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.
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
I rooted my Huawei y360 today. An update came to my phone from Huawei and I downloaded and installed it. The phone restarted and now is stuck in bootlog -it won't restart fully. It keeps coming up in recovery mode....... I need HELP!
shem_christoph said:
I rooted my Huawei y360 today. An update came to my phone from Huawei and I downloaded and installed it. The phone restarted and now is stuck in bootlog -it won't restart fully. It keeps coming up in recovery mode....... I need HELP!
Click to expand...
Click to collapse
I had the same thing. It looks like Huawei bricks the phone on purpose. Not very customer friendly
Here's how to unbrick :
Download a Huawei stock firmware, for instance from
http://consumer.huawei.com/nl/support/downloads/detail/index.htm?id=77123&key4=Y360&key5=webisearch
This particular version is 2016-3-25 V100R001C577B113 847.34 MB
Unzip the file and copy dload/update.zip including the directory to the root of an sd card.
Then press Vol-UP and Power at the same time, and select install updates. Done.
i have an problem my huawei y360 is giving me problem its trying to load up and stop a went to the bootlog so am trying to custom rom it because i dont have any assess to the phone.
hello.
i have the same issue here with my y360.
after i did kingroot and restarted my phone after an update only the logo boot remained.
the fw update from sd card didnt work because the phone doesn't recognize the card, afterwards i tried to flash it with the sp flash tool (old and new versions) but it was either ''invalid scatter file'' or ''dram error something...'' ofcourse i tried different fw versions but nothing worked.
anybody has an idea what to do or i should throw it to the garbage? thanks
I have the same thing going on. Trying to fix y360 for my nephew. Keeps bootlooping. It's stock.
Tried to use SP Flash Tool, but it keeps nagging about a faulty scatter.txt file, even though I downloaded the newest firmware directly from Huawei (so it has to be the right one).
I then tried to do an ADB sideload, that's what I can access right now. adb sideload update.zip (from inside the manufacturer's .rar file).
adb push does not work because ADB is not recognised, because the phone won't turn on.
Goes ok until 53% and then crashes. Internal memory runs out?
From what I can find,I should push the dload folder to sdcard, but I can't, because I can't mount the external sdcard to transfer the folder to.
So, my only option seems to be to borrow someone's phone with a microSD slot to transfer the folder, then change the card to the y360? Or get an adapter SD->microSD, then transfer the folder? Neither of which are available to me right now. Is this for real?
Damn, I miss the fastboot flash system system.img command of the more advanced phones.
70% of the instructions about this model bricking are in Spanish, so it is kind of hard to figure out what to do.
shem_christoph said:
I rooted my Huawei y360 today. An update came to my phone from Huawei and I downloaded and installed it. The phone restarted and now is stuck in bootlog -it won't restart fully. It keeps coming up in recovery mode....... I need HELP!
Click to expand...
Click to collapse
try to flash stock rom
Hi there! I'm hoping someone on XDA Developers can help me sort out a root gone-wrong.
I did my best to follow the guide on XDA. I have an Umidigi A9 Pro with 6gb ram. I was successfully able to get the android tools on PC and was able to unlock the bootloader. I went to the Umidigi website to get the ROM. I think I *might* have grabbed the wrong one. Once I got this zip from the Umidigi website, I unzipped the folder and copied the boot.img that was in that root folder to the device. I then went into Magisk and patched the img. I then copied the patched img to my PC then use the commands on the XDA guide to flash the image to the device, the flash was successful (I think). However the device is now stuck in a boot loop. The device displays the Umidigi OEM logo and the android logo; underneath it says in small text:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
after 5 seconds the screen goes black and then comes back with the same screen. This happens continuously. I have tried holding the volume down, the power button, and several combinations of volume up, down, and power. Holding all buttons down makes the screen stay black, however while plugged into the PC the PC still makes the device connected and disconnected sounds off and on. Whenever I release the buttons, it goes right back to the loop. Windows PC plays the device connected and disconnected sound on and off. The command prompt is not able to affect the device. When I run "adb devices" it doesn't display the phone so it doesn't seem that windows is detecting the device.
ROM: https://community.umidigi.com/forum.php?mod=viewthread&tid=22236&extra=page=1
https://www.umidigi.com/page-Download.html
I'm hoping for some help on this one
Thank you!
It should be obvious that when being in a bootloop ADB cannot function: On Android side the ADB daemon gets started and after seconds closed, and this over and over again.
In the simplest explanation, a bootloop describes when your phone is stuck in a loop of rebooting. The term "bootloop" is just a more common way of saying "reboot loop."
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Zeidwinder said:
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Click to expand...
Click to collapse
I honestly haven't messed with it since. It was a very cheap extra android phone I had laying around. Once it got messed up I pretty much just put it in a drawer and said "maybe another day"