Can someone pls. help me. I have a rooted Lenovo IdeaTab A3000-H that accidentally got soft bricked after I edited build.prop on /system/build.prop
Info:
Model Number: Lenovo A3000-H
Android Version: 4.2.2
USB Debugging: Disabled
Currently Bootable To: Stock Recovery and Fastboot
(I could boot to ADB but it could only do sideload commands)
I have a recovery.img (CWM) that I can't flash since my PC can't detect my tablet while it's turned off
(And also if possible, can someone give me an original unmodded Lenovo A3000-H build.prop.bak and CWM flashable zip compatible for my tab.)
Hello,
Welcome to XDA.
If you can get in fastboot mode you should be able to flash a CWM recovery.img, no need for a CWM flashable zip.
You can also try adb pushing a copy of your original build.prop to replace the faulty one, you can extract it from your stock firmware if its available for download and use the extracted copy or you can extract the build.prop from whatever custom ROM you were on if you had Custom installed.
I'm not saying these are your definite fix, they are just some things for you to look into.
Droidriven said:
Hello,
Welcome to XDA.
If you can get in fastboot mode you should be able to flash a CWM recovery.img, no need for a CWM flashable zip.
You can also try adb pushing a copy of your original build.prop to replace the faulty one, you can extract it from your stock firmware if its available for download and use the extracted copy or you can extract the build.prop from whatever custom ROM you were on if you had Custom installed.
I'm not saying these are your definite fix, they are just some things for you to look into.
Click to expand...
Click to collapse
1) it says that my tablet doesnt support flashing partitions through flashboot
2) my backup for my build.prop is in my internal storage(phone storage). And that is why I'm asking if any of you guys have an original copy of build.prop.bak so that I could try to flash it using my stock recovery
3) whenever I try to do adb commands, I always get the error "error:closed"
PS: I only have stock recovery and I can't flash using SP Flash Tool because I don't have my USB Debugging turned on
BTW sorry if I sometimes/always reply late... It's because my timezone is different, because I live in the Eastern Countries...
CEDoromal said:
1) it says that my tablet doesnt support flashing partitions through flashboot
2) my backup for my build.prop is in my internal storage(phone storage). And that is why I'm asking if any of you guys have an original copy of build.prop.bak so that I could try to flash it using my stock recovery
3) whenever I try to do adb commands, I always get the error "error:closed"
PS: I only have stock recovery and I can't flash using SP Flash Tool because I don't have my USB Debugging turned on
BTW sorry if I sometimes/always reply late... It's because my timezone is different, because I live in the Eastern Countries...
Click to expand...
Click to collapse
If you can find your stock firmware and download it you can extract your build.prop from it and adb push it to your system folder.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
If you can find your stock firmware and download it you can extract your build.prop from it and adb push it to your system folder.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I'm glad to know that... But I can't do any adb commands except for adb sideload because I always gets error:closed when I try to...
CEDoromal said:
I'm glad to know that... But I can't do any adb commands except for adb sideload because I always gets error:closed when I try to...
Click to expand...
Click to collapse
That's because you don't have USB debugging turned on, without that turned on your only option is to restore your device with your stock firmware. I don't think you are going to get much as far as answers here at XDA, you should take the device to a repair shop.
If you can boot to fastboot then you should be able to flash your stock firmware and restore the device.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
That's because you don't have USB debugging turned on, without that turned on your only option is to restore your device with your stock firmware. I don't think you are going to get much as far as answers here at XDA, you should take the device to a repair shop.
If you can boot to fastboot then you should be able to flash your stock firmware and restore the device.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
well... I think I could repair my device if someone gives me a CWM Recovery Zip compatible to Lenovo A3000-H that I could flash to my device using my Stock Recovery then use it so that my computer detects my device.... Or just an original copy of Lenovo A3000-H build.prop.bak or just build.prop.... Or a scatter file for my tab...
I could boot to fastboot but it says that it doesnt support flashing partitions using fastboot...
CEDoromal said:
well... I think I could repair my device if someone gives me a CWM Recovery Zip compatible to Lenovo A3000-H that I could flash to my device using my Stock Recovery then use it so that my computer detects my device.... Or just an original copy of Lenovo A3000-H build.prop.bak or just build.prop.... Or a scatter file for my tab...
I could boot to fastboot but it says that it doesnt support flashing partitions using fastboot...
Click to expand...
Click to collapse
I don't believe flashing a custom recovery through your stock recovery is even possible. You can't flash custom through stock recovery, you can only flash stock files and updates through stock recovery.
If you get the build.prop how do you plan to put it back where it goes? You said that USB debugging is not turned on so adb won't work, thats probably why fastboot isn't working either.
If you want to try the build.prop then download your stock firmware and extract the build.prop file from the firmware and use the extracted file.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
I don't believe flashing a custom recovery through your stock recovery is even possible. You can't flash custom through stock recovery, you can only flash stock files and updates through stock recovery.
If you get the build.prop how do you plan to put it back where it goes? You said that USB debugging is not turned on so adb won't work, thats probably why fastboot isn't working either.
If you want to try the build.prop then download your stock firmware and extract the build.prop file from the firmware and use the extracted file.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks for informing me...
Actually I'm planning to put that build.prop or build.prop.bak on a flashable Zip that I could flash to my /system....
and I'm not 100% sure if that's gonna work....
CEDoromal said:
Thanks for informing me...
Actually I'm planning to put that build.prop or build.prop.bak on a flashable Zip that I could flash to my /system....
and I'm not 100% sure if that's gonna work....
Click to expand...
Click to collapse
If you mean to flash it through stock recovery I doubt it will work, you can see if there are any stock updates in zip format for your model that can be flashed in stock recovery, if you were rooted it probably won't work though because you have to be unrooted and have an unmodified system partition to apply a stock update.
Your device isn't hard bricked yet so there should be something you can do, I just don't know the details of your model. You may have to take it to a repair shop.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
If you mean to flash it through stock recovery I doubt it will work, you can see if there are any stock updates in zip format for your model that can be flashed in stock recovery, if you were rooted it probably won't work though because you have to be unrooted and have an unmodified system partition to apply a stock update.
Your device isn't hard bricked yet so there should be something you can do, I just don't know the details of your model. You nay have to take it to a repair shop.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks for informing me again...
But I guess you won't achieve something unless you try...
BTW my friend is a community member here, and he said that it might work if I flashed build.prop.bak to the system. So I might as well try it....
I tried to use the SP Flash Tool to flash the recovery.img to my device but it got an error 3038 (I think), so I'm guessing it's the scatter file... (I Googled it )
CEDoromal said:
Thanks for informing me again...
But I guess you won't achieve something unless you try...
BTW my friend is a community member here, and he said that it might work if I flashed build.prop.bak to the system. So I might as well try it....
I tried to use the SP Flash Tool to flash the recovery.img to my device but it got an error 3038 (I think), so I'm guessing it's the scatter file... (I Googled it )
Click to expand...
Click to collapse
In your circumstances anything is worth trying.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
In your circumstances anything is worth trying.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
It won't Hard Brick my device right?
(warn me if it will make my problem worse.)
CEDoromal said:
It won't Hard Brick my device right?
(warn me if it will make my problem worse.)
Click to expand...
Click to collapse
I don't think so but don't quote me, it'll either flash an succeed or fail, I doubt it will make things worse.
Have you looked at the possibility of using an extsdcard and a debrick.IMG or its equivalent to boot from a bootable extsdcard the same as PC does with a bootable USB? If it works on your device like it does some other devices you can boot into system from extsd and then do what you need to do to fix your device then return the sdcard to normal use after you are going again on its own.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
If you mean to flash it through stock recovery I doubt it will work, you can see if there are any stock updates in zip format for your model that can be flashed in stock recovery, if you were rooted it probably won't work though because you have to be unrooted and have an unmodified system partition to apply a stock update.
Your device isn't hard bricked yet so there should be something you can do, I just don't know the details of your model. You may have to take it to a repair shop.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Can you tell this to the admin just to see if he could help me...?
and also, do you know why my tablet keeps disconnecting to my pc after 3 seconds when I'm trying to flash?
CEDoromal said:
Can you tell this to the admin just to see if he could help me...?
and also, do you know why my tablet keeps disconnecting to my pc after 3 seconds when I'm trying to flash?
Click to expand...
Click to collapse
An admin won't be able to help you. All android devices are different, they vary drastically from one model to the next, no one here knows about every device, you are going to have to find other users with your device or you will have to find a developer that works on your device, they will know what you need, we aren't all experts with all devices, we each know the devices that we have personally owned and used.
The disconnecting every three seconds is because you are still in a bootloop, it boots to flash mode then loops and boots again, over and over, it can't find the right stuff to boot the way it needs to.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
An admin won't be able to help you. All android devices are different, they vary drastically from one model to the next, no one here knows about every device, you are going to have to find other users with your device or you will have to find a developer that works on your device, they will know what you need, we aren't all experts with all devices, we each know the devices that we have personally owned and used.
The disconnecting every three seconds is because you are still in a bootloop, it boots to flash mode then loops and boots again, over and over, it can't find the right stuff to boot the way it needs to.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I think I just hard bricked my device....
I tried to install the recovery.img (said to be compatible to my device) using SP Flash Tool then it doesnt boot to anything now, but it is now detected on my pc even after 3 seconds.... (I got an error that is starting on a number 5 followed by three other numbers... sorry I forgot what it was...)
CEDoromal said:
I think I just hard bricked my device....
I tried to install the recovery.img (said to be compatible to my device) using SP Flash Tool then it doesnt boot to anything now, but it is now detected on my pc even after 3 seconds.... (I got an error that is starting on a number 5 followed by three other numbers... sorry I forgot what it was...)
Click to expand...
Click to collapse
Our purpose here at XDA Assist is to point you in the direction you need to look for your answers, we are not here to help you with every step until your device is fixed. I gave you suggestions for where you need to look for your answers because that is where you will most likely find your answers. If you do not find your answers where you were sent, that does not mean to come back here continuing to ask, I have done all that I can for you, I'm sorry that it is not helping you. Your device is unknown to me, the fact you are getting no answers in the forums means that the members in the forums also do not know your device, if they did then they would answer you. There is no guarantee that you will find your answer on XDA, we can only help with the devices we are familiar with. I don't think anyone here knows anything about your device because I did not find a lot of information about your device when I did a search of all the XDA forums because the information you need does not exist here in the forums, only another user that is experienced with your device can help you. You are going to have to find someone in the forums that also owns your device. Continuing to post here will not help you. Be patient and search through the forums by using your device model number in your searches here. If what you need is here then you will find it if you dig through all the threads that are associated to your device model number.
If you can not find an answer here then you will have to consider taking your device to a repair shop.
Droidriven said:
Our purpose here at XDA Assist is to point you in the direction you need to look for your answers, we are not here to help you with every step until your device is fixed. I gave you suggestions for where you need to look for your answers because that is where you will most likely find your answers. If you do not find your answers where you were sent, that does not mean to come back here continuing to ask, I have done all that I can for you, I'm sorry that it is not helping you. Your device is unknown to me, the fact you are getting no answers in the forums means that the members in the forums also do not know your device, if they did then they would answer you. There is no guarantee that you will find your answer on XDA, we can only help with the devices we are familiar with. I don't think anyone here knows anything about your device because I did not find a lot of information about your device when I did a search of all the XDA forums because the information you need does not exist here in the forums, only another user that is experienced with your device can help you. You are going to have to find someone in the forums that also owns your device. Continuing to post here will not help you. Be patient and search through the forums by using your device model number in your searches here. If what you need is here then you will find it if you dig through all the threads that are associated to your device model number.
If you can not find an answer here then you will have to consider taking your device to a repair shop.
Click to expand...
Click to collapse
I just fixed it using META mode without any help of XDA... >
Droidriven said:
Our purpose here at XDA Assist is to point you in the direction you need to look for your answers, we are not here to help you with every step until your device is fixed. I gave you suggestions for where you need to look for your answers because that is where you will most likely find your answers. If you do not find your answers where you were sent, that does not mean to come back here continuing to ask, I have done all that I can for you, I'm sorry that it is not helping you. Your device is unknown to me, the fact you are getting no answers in the forums means that the members in the forums also do not know your device, if they did then they would answer you. There is no guarantee that you will find your answer on XDA, we can only help with the devices we are familiar with. I don't think anyone here knows anything about your device because I did not find a lot of information about your device when I did a search of all the XDA forums because the information you need does not exist here in the forums, only another user that is experienced with your device can help you. You are going to have to find someone in the forums that also owns your device. Continuing to post here will not help you. Be patient and search through the forums by using your device model number in your searches here. If what you need is here then you will find it if you dig through all the threads that are associated to your device model number.
If you can not find an answer here then you will have to consider taking your device to a repair shop.
Click to expand...
Click to collapse
I just fixed it using META mode without any help of XDA or a repair shop... >
Related
Could anyone upload a stock build.prop back up of the note 3. i tried getting tegra effects on my device and ended up with the black screen of death
1- Wrong forum
2- What is your model number?
3- BLACK screen of death?
Sent from my SM-N900W8
yulet said:
1- Wrong forum
2- What is your model number?
3- BLACK screen of death?
Sent from my SM-N900W8
Click to expand...
Click to collapse
N900 i know this is the wrong forum sorry, i kinda needs this though. can get into recovery can get into download mode odin detects however i it doesnt boot past the startup screen. doesnt even get to the boot animation.
zephyr69 said:
N900 i know this is the wrong forum sorry, i kinda needs this though. can get into recovery can get into download mode odin detects however i it doesnt boot past the startup screen. doesnt even get to the boot animation.
Click to expand...
Click to collapse
Just flash the stock ROM for your model with ODIN. It'll take less time than waiting for somebody to post the file (unless.. a miracle happens.).
Sent from my SM-N900W8
yulet said:
Just flash the stock ROM for your model with ODIN. It'll take less time than waiting for somebody to post the file (unless.. a miracle happens.).
Sent from my SM-N900W8
Click to expand...
Click to collapse
I figured however i have limited bandwith where i am now and will only be able to download the stock next weekend. want to get my phone up and running asap
Have you got an authorised PC to push the file from? I'm certain to get adb access in 4.3, you get prompted to authorise the connecting machine, a security feature, if that's the case and you haven't done it, you may not new able to rectify your phone anyway, without the full firmware?
Sent from my SM-N9005 using Tapatalk
RavenY2K3 said:
Have you got an authorised PC to push the file from? I'm certain to get adb access in 4.3, you get prompted to authorise the connecting machine, a security feature, if that's the case and you haven't done it, you may not new able to rectify your phone anyway, without the full firmware?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
i havent pushed the file via ADB, i have done so using build.prop editor. i then by accident wiped my internal sd thus having no back up of the file. i just need the stock build.prop file so that i can push it back via custom recovery.
Please Help! after adding a line in build.prop to use android l bar my phone is black
Dear all,
after I add a line in build.prop (qemu.hw.mainkey=0)to get android l bar.
After restart I get black screen. so now I like to change back to my safe file.
have someone solution for me to get back my device?
I use Note 3 n9005 kitkat 4.4.2 . rooted.
how I can push this file via adb? even my device is not listed.
I really hope someone can help me
thanks in advanced
Try to flash stock firmware via Odin?
vndnguyen said:
Try to flash stock firmware via Odin?
Click to expand...
Click to collapse
thx for answer me.
is this the only solution I have?
jokertest said:
Dear all,
after I add a line in build.prop (qemu.hw.mainkey=0)to get android l bar.
After restart I get black screen. so now I like to change back to my safe file.
have someone solution for me to get back my device?
I use Note 3 n9005 kitkat 4.4.2 . rooted.
how I can push this file via adb? even my device is not listed.
I really hope someone can help me
thanks in advanced
Click to expand...
Click to collapse
Can you get into recovery?
AO7 said:
Can you get into recovery?
Click to expand...
Click to collapse
Yes I can get recover and download mode. so I tried adb but windows not load my device. so adb pull /system/build.prop not work. is it possible do use apply update from adb or use a update.zip via external storage, if yes how do I have to make this zip?
jokertest said:
Yes I can get recover and download mode. so I tried adb but windows not load my device. so adb pull /system/build.prop not work. is it possible do use apply update from adb or use a update.zip via external storage, if yes how do I have to make this zip?
Click to expand...
Click to collapse
Check to make sure if the correct driver for your device has been installed.
You can install Kies to get the driver also installed.
vndnguyen said:
Check to make sure if the correct driver for your device has been installed.
You can install Kies to get the driver also installed.
Click to expand...
Click to collapse
The Driver and adb work correctly you can see in my pic.
the first is my phone without listing and the second is from my wife with listed.
jokertest said:
is it possible do use apply update from adb or use a update.zip via external storage, if yes how do I have to make this zip?
Click to expand...
Click to collapse
Check these thread, I have not tested it.
http://forum.xda-developers.com/showthread.php?t=2163974
http://www.xda-developers.com/android/easily-create-recovery-compatible-archives-with-zip-creator/
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=269061234
vndnguyen said:
Check these thread, I have not tested it.
http://forum.xda-developers.com/showthread.php?t=2163974
http://www.xda-developers.com/android/easily-create-recovery-compatible-archives-with-zip-creator/
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=269061234
Click to expand...
Click to collapse
I tried this but not work.
I get: footer wrong and signature verification failed. I tried this via adb side load and update from external storage.
usb driver in windows will only load in adb sideload
another idea?
Have you tried factory restore?
I'm not sure but maybe it would rebuild it?
MystaMagoo said:
Have you tried factory restore?
I'm not sure but maybe it would rebuild it?
Click to expand...
Click to collapse
mmh just tried but same state as before.
so I really think I have to flash stock rom. But how about the root. I use towelroot before so knoxx show 0x0.
will flash stockroom change knoxx 0x1. Any special for flash stockrom?
zephyr69 said:
Could anyone upload a stock build.prop back up of the note 3. i tried getting tegra effects on my device and ended up with the black screen of death
Click to expand...
Click to collapse
you should always make a copy of the rom, I have roms and firmwares at my site...
happened to me 2 days ago, I changed one hltexx to hlte or hltetmo to get my correct icons, and black screen, I just flash my good rom, keep a good copy on your sdcard or ext. so u can flash back, or restore ur backup nandroid copy.
http://www.androidfilehost.com/?w=devices&uid=9390248398092763634
zephyr69 said:
Could anyone upload a stock build.prop back up of the note 3. i tried getting tegra effects on my device and ended up with the black screen of death
Click to expand...
Click to collapse
here is my back up build.prop from note 3 n9005 UK without the f...g line I add for l bar. hope you can push to your device and it work.
for me I not have solution to get my phone to run
guys I changed my dpi with this app
https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi&hl=en
textdroider dpi now i am in a boot loop
my phone is rooted but i dont have any custom recovery installed on it.
I took a backup on my sdcard of that build.prop and i guess the app gets one also but is there a way I can change the faulty one?
As I said I only had stock recovery is it possible to adb with that? Or is my only chance is to flash stock rom again
as it is described on this topic http://forum.xda-developers.com/showthread.php?t=2432476
if so which rom should I download I live in Australia and got and Australian stock phone. Should I download d802 Asia?
Thanks for all the help I would really appreciate if I can save it without losing my data but if thats the only way what can I do.
I hope you have a custom ROM or the ROM you have already flashed. Just make a flashable zip with the build.prop placed in /system/ .
flash it through recovery and you are back again..
Or just flash your Rom again. Should fix the issue
Sent from my VS980 4G using XDA Premium 4 mobile app
Guys I am a complete newbie. Can you please explain it more to me.
I am currently downloading the .kdz file via this software
http://forum.xda-developers.com/showthread.php?t=1073827
also i did found this http://forums.whirlpool.net.au/forum-replies.cfm?t=2186883&p=6&#r106
so i am pretty sure I am downloading the right rom right now because the software pickup the same name.
So am I right about flashing my phone by following the steps on the topic I mentioned in my first post?
Is this what you mean by flashing trought recovery because that dude says download mode.
BTW I cant flash trought lg's utility I dont know if its related or not but windows cant install CDC driver.
Also when I flash the rom am I going to lose my data.
Thanks for your answers guys really appericate it.
Just adb the build.prop...
No, download mode it's a form of diagnostic mode, recovery doesn't matter.
You will lose everything. Read and learn, test and perform, only you can make yourself not a noob.
Steamer86 said:
Just adb the build.prop...
No, download mode it's a form of diagnostic mode, recovery doesn't matter.
You will lose everything. Read and learn, test and perform, only you can make yourself not a noob.
Click to expand...
Click to collapse
How can I adb the build.prop ?
I can only go into LG G2 Stock recovery mode and download mode. There is no custom recovery installed so I cant open debugging and adb doesnt recognize the device.
Am i doing something wrong? and believe me I have been reading for hours
I can't explain it much further, your gonna have to search forums. There was a recent thread on this with koushs driver and some lines to force recognize. I don't remember were or what.
Steamer86 said:
I can't explain it much further, your gonna have to search forums. There was a recent thread on this with koushs driver and some lines to force recognize. I don't remember were or what.
Click to expand...
Click to collapse
but even that needs custom recovery I dont have custom recovery unfortunately ((
It does not...
capuagenclik said:
guys I changed my dpi with this app
https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi&hl=en
textdroider dpi now i am in a boot loop
my phone is rooted but i dont have any custom recovery installed on it.
I took a backup on my sdcard of that build.prop and i guess the app gets one also but is there a way I can change the faulty one?
As I said I only had stock recovery is it possible to adb with that? Or is my only chance is to flash stock rom again
as it is described on this topic http://forum.xda-developers.com/showthread.php?t=2432476
if so which rom should I download I live in Australia and got and Australian stock phone. Should I download d802 Asia?
Thanks for all the help I would really appreciate if I can save it without losing my data but if thats the only way what can I do.
Click to expand...
Click to collapse
I bootlooped changing my dpi as well. I was stock rooted with no custom recovery. I followed the instructions here http://forum.xda-developers.com/showthread.php?t=2471370&highlight=unbrick and was able to get my phone to work again. FYI, it may install the latest firmware for your phone, even if it's not OTA yet, and ioroot might not support it yet if it does. I have a d801 and it installed the latest firmware, although it wasn't OTA yet. Hope this helps.
Howie Dub said:
I bootlooped changing my dpi as well. I was stock rooted with no custom recovery. I followed the instructions here http://forum.xda-developers.com/showthread.php?t=2471370&highlight=unbrick and was able to get my phone to work again. FYI, it may install the latest firmware for your phone, even if it's not OTA yet, and ioroot might not support it yet if it does. I have a d801 and it installed the latest firmware, although it wasn't OTA yet. Hope this helps.
Click to expand...
Click to collapse
Ahh mate it would probably helped because my support tool couldnt recognize my device as d802 but instead l02e or l20e sth like that with united driver but I reckon those are the drivers I was looking for unfortunately I dont have the phone anymore.
I turned the phone back to the warranty today not giving any explanation to try my luck. they may just do this same procedure and just flash stock rom on the service and send it back to me or they might just say this is rooted its out of warranty either case I will let them deal with it if they say this is out of warranty I will ask them to fix it and I am willing to pay if they quote me something reasonable if they dont I will try this.
Thank you very much for your answer.
If they say rooted and stuff and outa warranty! Just get it back home.. I will help you via teamviewer!
Jishnu Sur™ said:
If they say rooted and stuff and outa warranty! Just get it back home.. I will help you via teamviewer!
Click to expand...
Click to collapse
Thank you heaps man how nice of you. I would let you guys know how it goes. Its only soft bricked so i think technical support would be able to flash the stock firmware on it but I hope they wont decide to give me hard time. If they do i am planning to play the fool
I will definitely pm you if I get it back unfixed. Thank you for the offer.
Jishnu Sur™ said:
If they say rooted and stuff and outa warranty! Just get it back home.. I will help you via teamviewer!
Click to expand...
Click to collapse
Hello i think my lg g2 is bootlooping will you be able to help through teamviewer plz thanks a lot
pilo99 said:
Hello i think my lg g2 is bootlooping will you be able to help through teamviewer plz thanks a lot
Click to expand...
Click to collapse
Please tell me how it happend??
Sent from my GT-N7000 using xda app-developers app
Jishnu Sur™ said:
Please tell me how it happend??
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
was playing with dpi density and it start doing the bootloop , i try to get back to stock through the lg flash utiliy and it did but no system setting and it keep turning on and off i can get to download mode ,,,,but the recovery it just show the green android man and then boot staright to the home screen
pilo99 said:
was playing with dpi density and it start doing the bootloop , i try to get back to stock through the lg flash utiliy and it did but no system setting and it keep turning on and off i can get to download mode ,,,,but the recovery it just show the green android man and then boot staright to the home screen
Click to expand...
Click to collapse
Check PM!
Jishnu Sur™ said:
Check PM!
Click to expand...
Click to collapse
cool am online now
Guys I just wanted to give you update on the matter. Today I called the repair centre and they told me they have fixed the phone and send it back yesterday so I should be able to get it in couple of days maybe this friday or next week monday something like that. They didnt say anything about root or warranty or stuff like that. When I get the phone back what can I do prevent this from happening again? Do I need to flash a custom recovery on the phone? What is the risk of doing that? Or should I just root the phone and not mess with the system files ever again
Thanks heaps for all your inputs.
Got the phone today they changed the motherboard. I am not sure if it is a good thing or a bad thing :/ On the good side it is fixed for good on the flipside the phone has been opened now so thats not so good. I have checked the body coudlnt find too many stracthes or sth like that they did a clean job but still.
Anyway that was the last update.
Hello there!
So, I'm using Zenfone 5 (2G) Running on Official Lolipop
I had my phone bootlooped back in that time, then I flashed a wrong recovery version, it was KitKat version that I flashed, I got into Recovery Mode.
I tried to sideload update packages (both KitKat and Lolipop ROM) and it showed me some error like can't mount /cache (invalid arguments), I expected this as losing partition (If I'm not wrong)
And now I can't even get into droidboot at all, here is the responds from following things I do :
Recovery button combination : Works (Gets to the recovery)
Power button : Shows USB logo
Droidboot button combination : Shows manufacturer logo forever (Stuck)
But, as I said, I tried to sideload the packs and it fails...
Could someone help me? Maybe some easy way to fix this? For a note, I tried bunch of tutorials to fix my device, the last one was xFSTK thing.. I followed every single step correctly and ended up with an error.
Thanks before
kelvinvalencio said:
Hello there!
So, I'm using Zenfone 5 (2G) Running on Official Lolipop
I had my phone bootlooped back in that time, then I flashed a wrong recovery version, it was KitKat version that I flashed, I got into Recovery Mode.
I tried to sideload update packages (both KitKat and Lolipop ROM) and it showed me some error like can't mount /cache (invalid arguments), I expected this as losing partition (If I'm not wrong)
And now I can't even get into droidboot at all, here is the responds from following things I do :
Recovery button combination : Works (Gets to the recovery)
Power button : Shows USB logo
Droidboot button combination : Shows manufacturer logo forever (Stuck)
But, as I said, I tried to sideload the packs and it fails...
Could someone help me? Maybe some easy way to fix this? For a note, I tried bunch of tutorials to fix my device, the last one was xFSTK thing.. I followed every single step correctly and ended up with an error.
Thanks before
Click to expand...
Click to collapse
Try this:
Download a flashable custom rom, put the rom *.zip file in the same folder with ADB.
Go into recovery TWRP, connect your phone to your computer.
Push rom *.zip file to your phone's internal storage with this command in ADB:
push [file.zip] /sdcard/.
Then flash that rom file with TWRP.
Well, sir, how can I get into TWRP? I can't even droidboot... My recovery that I flashed was stock
deleted.
kelvinvalencio said:
Hello there!
So, I'm using Zenfone 5 (2G) Running on Official Lolipop
I had my phone bootlooped back in that time, then I flashed a wrong recovery version, it was KitKat version that I flashed, I got into Recovery Mode.
I tried to sideload update packages (both KitKat and Lolipop ROM) and it showed me some error like can't mount /cache (invalid arguments), I expected this as losing partition (If I'm not wrong)
And now I can't even get into droidboot at all, here is the responds from following things I do :
Recovery button combination : Works (Gets to the recovery)
Power button : Shows USB logo
Droidboot button combination : Shows manufacturer logo forever (Stuck)
But, as I said, I tried to sideload the packs and it fails...
Could someone help me? Maybe some easy way to fix this? For a note, I tried bunch of tutorials to fix my device, the last one was xFSTK thing.. I followed every single step correctly and ended up with an error.
Thanks before
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/zenfone-5/general/zenfonetoolkit3-24-40-87-t3406557
tank4k said:
can u open droid boot?
Click to expand...
Click to collapse
No
paktepu said:
Try this
http://forum.xda-developers.com/zenfone-5/general/zenfonetoolkit3-24-40-87-t3406557
Click to expand...
Click to collapse
Got your post.. Didn't download..
I want to make sure one thing.. Does this work on TW SKU? Because It's writen that your file is integrated with WW SKU
kelvinvalencio said:
Got your post.. Didn't download..
I want to make sure one thing.. Does this work on TW SKU? Because It's writen that your file is integrated with WW SKU
Click to expand...
Click to collapse
Basicly the procedure to debrick is same. You need to load bootloader temporary since you have a broken droidboot including your partition. I already have same problem with you before.
Yeah its different, you cant use ww to fix this. Find on official zentalk tw forum for complete detail. Shakalaca post that.
Sent from my ASUS_T00F using XDA-Developers mobile app
paktepu said:
Basicly the procedure to debrick is same. You need to load bootloader temporary since you have a broken droidboot including your partition. I already have same problem with you before.
Yeah its different, you cant use ww to fix this. Find on official zentalk tw forum for complete detail. Shakalaca post that.
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks a lot!
Anyway, I've got few questions left..
Yesterday, I did download zip files from this debrick thread (Should be familiar with you) http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
My question is, does this work the same as your files? And, could I do something about it? Like re-use by recycle again the files I've downloaded with something that might help my phone? You know.. 900 MB is not something very small for me.. And maybe I could download separated files that is required.. And make the use of Debrick files I downloaded?
And.. May I have the link of Shakalaca's post, if you don't mind? Thanks a lot, like a lot!
kelvinvalencio said:
Thanks a lot!
Anyway, I've got few questions left..
Yesterday, I did download zip files from this debrick thread (Should be familiar with you) http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
My question is, does this work the same as your files? And, could I do something about it? Like re-use by recycle again the files I've downloaded with something that might help my phone? You know.. 900 MB is not something very small for me.. And maybe I could download separated files that is required.. And make the use of Debrick files I downloaded?
And.. May I have the link of Shakalaca's post, if you don't mind? Thanks a lot, like a lot!
Click to expand...
Click to collapse
Yes you can do manual from that link but from step 8 download tw.zip.
Cek pm for shakalaca
Sent from my ASUS_T00F using XDA-Developers mobile app
paktepu said:
Yes you can do manual from that link but from step 8 download tw.zip.
Cek pm for shakalaca
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
Hey um, I followed the Debrick one. The problem comes when I ran Debrick.dat, from the Cloverview mode (Press vol down and connect to pc). While the Debrick program runs, the phone "boots". Shows up USB logo and it goes red. Few seconds after then, the program closes, leaves the phone on red USB logo. Is this something normal?
Btw that link can't help.
Sent from my EG680 using XDA-Developers mobile app
Didn't you try reboot from bootloader. If it solves, it means normal. You must thank to intel for this problem.
---------- Post added at 09:07 PM ---------- Previous post was at 09:03 PM ----------
DogeLordTR said:
Didn't you try reboot from bootloader. If it solves, it means normal. You must thank to intel for this problem.
Click to expand...
Click to collapse
OK, I'm really stupid, sorry for time waste.
paktepu said:
Yes you can do manual from that link but from step 8 download tw.zip.
Cek pm for shakalaca
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
Hey um, I have contacted Shakalaca and until today I have not retrieved any reply. This problem haven't been solved. Any idea? I see you know a lot about this, and you're very popular arround here.
This happened with my Asus Zenfone 5 (T00j). Tried every solution available on net without sucess, finally took it to Service Center and they had to replace the motherboard
Hi guys!
I would just like to start by apologizing for making another thread about a bricked note4, however I have read about so much I don't know which advice to go with anymore. I'm also a complete novice when it comes to this.
So long story short, my note 4 started playing up and lagging, eventually not turning back on at all. After endless attempts using odin and flashing what I seemed to have thought was the right firmware, it whittled down to about 1 in 5 attempts of trying to enter download mode (using the buttons) on the phone actually working. Now its completely bricked...no power, no download mode, nothing!
Just like to reiterate, I'm a complete novice,sorry if I'm not making sense, my knowledge doesn't go further than articles and google!
I have tried using kies to recover my phone and it cant recognize it...
I have read about using adb to get my phone into download mode, but I couldn't understand the explanation given well enough to use it...
I bought a 16gb micro sd card and have tried writing an unbrick image to it but I get no response off my phone, also tried another file, possibly sdc? cdc? cant quite remember, but that failed too.
I don't even know if the files I'm using are correct, I got them from a forum on here.
I'm at a loss!
The only hope I have left is if someone is able tell me if any steps I have tried are correct, and possibly provide me with the correct unbrick image?
Also, when I plug my phone into my computer via usb, there is a noise that sounds but nothing else happens, don't know if these means anything. As far as I'm aware I also have correct drivers installed.
Sorry about the long explanation!
Any help is greatly appreciated!
Thanks in advance.
Lucy.
Only logical result from your explanation is you have a hardware problem.
I dont think you are gonna be able to solve it with software...
Time for service visit i guess..
Turkawa said:
Only logical result from your explanation is you have a hardware problem.
I dont think you are gonna be able to solve it with software...
Time for service visit i guess..
Click to expand...
Click to collapse
Thanks for the reply!
I hope that's not the case forgot to mention,when I plug my phone into a computer and go into device manager, it shows qhsusb_bulk...if this means anything to you?
Lucyhenn123 said:
Thanks for the reply!
I hope that's not the case forgot to mention,when I plug my phone into a computer and go into device manager, it shows qhsusb_bulk...if this means anything to you?
Click to expand...
Click to collapse
Nope.. I have no idea.. Sorry
Try the sd recovery method .
First you can try to flash the pit partion .
You can find that on xda .
Just search for note 4 pit files.
Download the n910f pit file with correct csc.
TRY flashing via download mode.
Try flashing .
Use this guide for using sd card to get into download mode if you cant access download mode
There is a method for http://cloud.tapatalk.com/s/57e756f41dc6e/read me for brick fix.txt
Reporting via N910G
Hi, everyone I tried to flash a new recovery on X00T but before I did this I Wiped all the data except internal storage. I Flashed the new recovery (completely forget about there being no OS) I rebooted to recovery and ignored the no OS message as the device rebooted I came on a black screen even the fast boot mode screen was black. I had no idea what to do so I tried to install the old TWRP from power shell/Adl so I could have a recovery and then install Custom rom again from recovery.
But there when I try to flash a file with command
-> Fastboot flash Recovery ....(..= file name)
It is shown completed on pc but on android even after rebooting I can't get anything except the black screen. This is what I get when I enter the following commands
-> fastboot devices
My devices number is shown
but if I type.
-> adl devices
My device is not shown.
But when I press the recovery buttons on device adl devices Is able to recognise device as a recovery screen device.
And the extra bonus on this is when I try to flash rom or fimware from adl. It says unable to read zip file.
So can anyone tell me if there is a way to fix this unable to read zip file problem. (I have tried uninstalling and reinstalling drivers from device manager & tried installing 64 bit files also)
Is there a command to flash rom from recovery. Or any way to fix this black screen
Thanks to everyone for reading any advice would be really helpful at this time.
Try using Asus Flash Tool to flash stock ROM
Tianhe said:
Try using Asus Flash Tool to flash stock ROM
Click to expand...
Click to collapse
Thanks for helping, Will surely try it. Can you please provide the link from where i can download flash tool?
Xda user 101 said:
Thanks for helping, Will surely try it. Can you please provide the link from where i can download flash tool?
Click to expand...
Click to collapse
I am not sure if posting external links (except hosting sites) is permitted. A simple google search or search within XDA will give you the results. In case you face difficulty, PM me.
Try to use this adb
If it still doesn't get detected, maybe use usb hub.
I wrote a thread guiding people on how to install stuff and my experience (issues) that is similar to yours. Not sure if my thread will help ya though
Vysair said:
Try to use this adb
If it still doesn't get detected, maybe use usb hub.
I wrote a thread guiding people on how to install stuff and my experience (issues) that is similar to yours. Not sure if my thread will help ya though
Click to expand...
Click to collapse
Bro tried as you said but didn't worked but finally found a solution. Now device is on and working again.
If anyone else face this issue I followed this thread https://forum.xda-developers.com/as...uide-revert-to-stock-rom-lock-t3798420/page46
It worked on my phone it is on again. Will have to root again but learned my lesson will never try new twrp when there is no os installed. :laugh:
thanks you Tianhe and Vysair for your advice for solving the issue.