Related
I did not see any thread for this so opening a new one so its easy to find.
I rooted my phone using gingerbreak and like a wiseazz, loaded a custom recovery image of "recovery-RA-GNM-thunderg-1.2". Although the costom recovery loaded fine, I am stuck with a phone which has only blue and green colors. I loaded one of the custom 2.3 ROMs by Andy and it loaded fine, but still the graphic display is all messed up, only green an blue and some other tinges. When I look at the About phone I see that it says the model number as LG P500 , although mine is LG P506. Any help people??
My wife will kill me. Its her phone!!
why would you flash a P500 ROM to a P506 ? did you make a backup ?
I made a backup of the ROM, but I did not backup the recovery.img.
Can I try NAND restore of the old ROM. I have my doubts if that would work, because as soon as I put the custom recovery in it. It started getting messy colors. But I will try. If any one else has any pointers please let me know.
Also, I ready in one of these posts that Thrive and Phoenix are just variants of Optimus One, architecturally same. Bad decision
Ok. An update. I did a Nandroid backup and I have the ROM which came with the phone. It sucks. But I guess I will have to wait till one of the brainys in here come up with a good "Custom Recovery" and "Custom ROM" for LG Thrive.
I have a LG Optimus T and the LG p500 roms work fine with no problems. I would of expected the same for the att version. I guess you have to wait for one that supports it.
Sent from my LG-P500 using XDA App
More bad news. I thought if I can mix and match boot.img of LG506 with the system.img of P500, I can get away by loading the Custom ROM.
Bad Bad Bad decision. Right now, its in a bricked stage. Basically stuck in something called..fastBoot udc_start()...
Its not getting to recovery mode whatever I do. I wanted to get to recovery so I can restore NAND backup. I can even get to adb so I can start in recovery....
Somebody help please
Can anyone help me. I tried all possible routes to unbrick my phone. It keeps getting wosre and worse. Right now its stuck in "Emergency Mode". I have the NAND backup file with system.img and boot.img, but cant do anything with it since no ADP or customer recovery. I tried to do a KDZ update, but I think i need the v11e_00.kdz file for P506. Can anyone give me some pointers to recver my phone.
I have a thrive as well and I get the weird blue green screen using the unofficial cm7 rom from the optimus dev section. Luckily I back up the phone with rom manager first so now im back to where I started.
edit: Well after your post I decided to try it again... mistake. Now im stuck at the cm7 logo and im not really sure how to fix it...
edit 2: cant load recovery either... ****
I have tried out the custom roms and i get the strange color problem too. It's strange how the cell phone board is P500 but the model is P506. The phone must be different somehow hardware wise. Hmm....
Ok. An update.
I bricked my phone trying to experiment. I sent it out to LG repair and they put in the stock ROM and sent back. I will not be continuing my experiments again
Can any big hearted rooters help the LG thrive owners please..
Do experiments but cautiously
Sent from my LG-P500 using XDA Premium App
I have a similar problem with my phone now. I flashed rom and now my phone gets stuck on boot screen. I can get to recovery. But my backups not there for sum reason.
Edit: I found what was supposed to be tha stock rom for my phone but didnt work. Gets stuck after lg screen goes away. It will go to recovery. Does anyone have a copy of a nand
Backup for a P506 thrive?
I've managed to get myself in the same situation would you happen to recall the LG number you called or have a lead on who I can contact at LG. I will continue to search also. Thanks in advance.
Ok wow. You need to go to WWW.androidcentral.com once there go to the Phoenix/ thrive thread. We have a custom kernel made by joban to run the p500 roms without the color issue. Also have how to threads for rooting, CWM, and flashing.
Running oxygen v1.1 w/ joban kernel,cwm on my LG Phoenix. And its awesome. Fast, great battery
Don't forget to hit the thanks button!
Sorry that it took me forever to get back to this, but just one question. Are the kernels for the Phoenix and Thrive exactly the same?
No issues that i can recall being specific to the kernel.
Question: I have rooted the phone and installed ROM Manager. Set up Rom Manager as Optimus One. Here is the issue: I am able to reboot normally and keep root. But when I select to reboot into recovery from ROM Manager, the phone does a default setup and I'm back to factory default. When I try to get into recovery by using the PWR+Home+Vol up (and vol down at times), I get into fastboot with "udc_start()". Which I'm guessing is normal. What am I missing to get into recovery?
Thanks.
Assuming you have a thrive. You may want to check this out.
http://forums.androidcentral.com/t-lg-phoenix-thrive/138186-how-clock-workrecovery-mod-cwm-6.html
There appears to be a hickup with thrive and CWM.
lg thrive p506 EMERGENCY MODE!
my lg thrive come on and immediately goes into emergency mode. i have been searching for about two weeks for anything that will help me in xda forums, and youtube and phandroid. i cant find anything that conclusively brings the phone out of emergency mode. can anyone direct me to a program or forum that might be of assistance?
need more info. are you on stock unrooted, just rooted, or rooted with custom recovery and rom?
what were you doing when this happened?
^^^^need to know^^^^^^^^^
try this and let me know what you get. hold at same time Home+vol down+power.
Hello,
I was wondering if someone could explain me, how BRICK happens or what to do to stay away from brick.
I searched for this question, but cannot find proper answers...
Thx in adv
TwinHeadedEagle said:
Hello,
I was wondering if someone could explain me, how BRICK happens or what to do to stay away from brick.
I searched for this question, but cannot find proper answers...
Thx in adv
Click to expand...
Click to collapse
It depends what device you have. Different things can cause different devices to brick. Usually a "bricked" device is caused by a bad kernel (more so by over clocking or overvolting), (If you have an HTC device) a bad HBoot, flashing a leak that is incomplete or flashing an update (RUU, Odin, whatever) for the wrong device, or flashing a package for the wrong device or one that is improperly coded.
You CANNOT brick your device by flashing custom roms and recoveries or anything like that, and permanent, unfixable, hard bricks are VERY rare and are usually because someone did something stupid.
If you're worried about installing a custom ROM or something, don't worry, it won't brick you.
TwinHeadedEagle said:
Hello,
I was wondering if someone could explain me, how BRICK happens or what to do to stay away from brick.
I searched for this question, but cannot find proper answers...
Thx in adv
Click to expand...
Click to collapse
Bricks happen when you try something not meant for your phone.
Sent from my U8150 using XDA
Thank you so much for clarifying this to me...
I am not total beginner, i possess Galaxy GT-I9001, for 4 months and i installed CWM last week, with complications, i used Odin 4.03 what one guy instructed to me, beside 4.43. First 4.03 failed and my phone failed to boot, I was worrying i could lose the phone. Then i used 4.43 from the Wiki tutorial what fixed the things...
Now i want to Root the phone, so this previous experience scared me, now i am not confident about it so I used to ask here...
So to clarify:
- rooting
-CWM
-flashing - installing custom ROMS
in proper way and following instructions won't brick my phone?
Is it possible that the dev/alpha/beta ROM versions could brick my phone?
How hard brick happens I am interested?
Is soft brick always fixable?
Sorry for bothering with this stupid questions, I am just not too confident, and i don't wanna destroy the phone, i've got no money for another
Thanks again and sorry if bad English
bricked= corrupted bootloader
a really bricked phone is like "dead' and the only way to solve this problem is to flash a new-and-happy bootloader by hardware tools like Medusa jtag jig also you can't solve bricked phone by PC software if yo do so then your phone is not really bricked
I don't know anything about hard/soft bricked what's that ??
you can't brick a phone by flashing a beta rom if you don't touch bootloader but you can destroy or cause hardware damage by flashing a rom/kernel not made for your phone so that's very important to know !
to prevent bricking your phone:
1. never use a flashing tool not made for your phone
2.when flashing bootloader made for your phone only use a stable PC connection/cable and is better to use a laptop on battery
3.about ROM Manager :if you don't see your phone in list never use it to flash recovery/rom
rooting means to get root access this is like your Administrator account in Windows OS well, it happens because by default phones come out from manufacturer with root disabled to protect the phone and their business
CWM is a custom recovery in fact this is a little OS that works like Safe Mode in Windows it can help you to flash a rom/update/theme etc
CWM recovery is different compared to stock recovery because it gives you the chance to flash custom things to your phone I mean you have to give a package a digital signature in order to flash it to your phone and stock recovery is restrictive it allows you to flash only signed-by-manufacturer things like roms/updates/themes and here is the place where CWM comes it allows to flash self-signed packages
Follow tutorials and you won't brick your phone. Stick to your device forum. E.g ,Just because something worked on the galaxy ace doesn't mean you can use that tutorial on a galaxy mini.
Soft bricks can be fixed,those are just installation errors.
Sent from my U8150 using XDA
I was wondering how to remove CWM and to restore original recovery...
I suppose i have to flash my stock ROM, am i right?
Do i need to wipe all data before flashing my custom ROM, just to add i have 2.3.3 i only did CWM nothing else is changed.
One thing isn't clear, when I flash CWM is my stock ROM changed?
TwinHeadedEagle said:
I was wondering how to remove CWM and to restore original recovery...
I suppose i have to flash my stock ROM, am i right?
Do i need to wipe all data before flashing my custom ROM, just to add i have 2.3.3 i only did CWM nothing else is changed.
One thing isn't clear, when I flash CWM is my stock ROM changed?
Click to expand...
Click to collapse
Why would you want to remove cwm? Its a custom recovery, without it you can't go custom. Use cwm to create a nand backup. To go back to stock recovery, you are correct, but make sure you have correct files etc in Odin. Pulling out your USB cable in Odin without completed will brick your phone, I know cuz I did it. The wrong files can do the same. CWM doesn't change the ROM, just the recovery. I have also heard of bricks from Samsung kies mini. Yes you need to wipe/ factory data reset when flashing a new ROM. If you are only updating a custom ROM, going from (ROM name) v 1.2 to (ROM name) v 1.3 it is not always necessary to do factory data reset but follow the instructions per developer of ROM/thread. Get root, put custom ROM on sd, in recovery make a nand backup, wipe cache, wipe dalvik cache, factory data reset, install zip from sd, reboot.
Also sometimes when flashing a ROM it might not boot first time. Don't panic, pull battery out/in 3 button to recovery, install zip again, reboot and enjoy.
Hope this helps....if so hit thanks button!
sent courtesy of the pony express
TwinHeadedEagle said:
I was wondering how to remove CWM and to restore original recovery...
I suppose i have to flash my stock ROM, am i right?
Do i need to wipe all data before flashing my custom ROM, just to add i have 2.3.3 i only did CWM nothing else is changed.
One thing isn't clear, when I flash CWM is my stock ROM changed?
Click to expand...
Click to collapse
No,your stock rom is not changed,just your recovery. You'll need clockworkmod do install custom roms since stock recovery lacks the features needed to install non-manufacturer roms.
If you are concerned about altering your current rom,you can make a backup using clockworkmod recovery, and store it somewhere like your PC.
Yes,just to be safe, it is better to wipe data. Unless it's an update of the same rom which again, isn't always guaranteed. Just to be sure your safe,backup your apps and clear everything.
Clockworkmod is removed in the bootloader by swapping it out with something else(like amon-ra).
Sent from my U8150 using XDA
Ok, thanks
I am planning to use custom roms, but it's not important at this time, I am satissfied with current...
I only need to know how to restore stock recovery, if the phone is somehow damaged and needs to be taken to the service warranty is lost with CWM installed?
Thank you and Sorry again if i am too noob, and asking stupid questions, i just need detailed explanations from people that experienced this, and apparently I've got it
TwinHeadedEagle said:
Ok, thanks
I am planning to use custom roms, but it's not important at this time, I am satissfied with current...
I only need to know how to restore stock recovery, if the phone is somehow damaged and needs to be taken to the service warranty is lost with CWM installed?
Thank you and Sorry again if i am too noob, and asking stupid questions, i just need detailed explanations from people that experienced this, and apparently I've got it
Click to expand...
Click to collapse
It is possible to reset the phone fully to stock. This removes clockworkmod recovery and your custom rom and allows you to claim warranty. So far only Sony is the one I'm aware void your warranty permanently if you unlock your bootloader using their 'official' method. They keep you on record,so even if you relock it you're outside warranty.
Sent from my U8150 using XDA
How To Unbrick my Kindle Fire?
Hello, I'm a Noobie,
I think I bricked my Kindle Fire. “kindle fire” stays on the screen when I turn it on. I can see the device on my computer as ‘Removable Disk (G’ however I am unable to access the drive. Am I BRICKED for good? Kindle running 6.3.1.; PC running Window 7. Please help…..
lcharrisej said:
Hello, I'm a Noobie,
I think I bricked my Kindle Fire. “kindle fire” stays on the screen when I turn it on. I can see the device on my computer as ‘Removable Disk (G’ however I am unable to access the drive. Am I BRICKED for good? Kindle running 6.3.1.; PC running Window 7. Please help…..
Click to expand...
Click to collapse
Redownload the rom with a stronger internet connection, flash it again.
Sent from my U8150 using XDA
@ Allanitomwesh
You didn't tell me how to reset phone fully to stock
I am assuming you haven't started playing with your phone.
Dial *#1234# and write down the three ID Strings PDA, CSC & PHONE ID
They'll be useful later. Just for paranoia, use adb to save your IMEI details (adb is for windows PC's don't worry)
Install Samsung Keis in same PC. Make sure it recognises your phone. Always check this before running Odin.
Always do a full backup (apps, data,settings) before resetting to stock or just any flashing.
Odin will install custom roms on your phone,and it will also take you back to stock if need arises. This is done by 'flashing' stock rom into your phone.
You can follow this tutorial
http://forum.xda-developers.com/showthread.php?t=1345671
Where the rom is the stock one. You can get the right one here http://www.sammobile.com/firmware/?page=1&t=2 Clockworkmod and root access will be lost.(those come with custom roms,don't worry)
When using Odin, a few tips,
1.always run as administrator (right click on icon>run as administrator)
2.Odin runs better without sim card and SD card. You can take them out before entering download mode
3.NEVER EVER interrupt a flashing process,its a guaranteed soft brick.It takes about 10 minutes. If you're impatient, walk away. Also for paranoia,better to have a ups.
4. Perform factory reset before and after flashing. * Menu* Settings* Privacy* Factory data reset* Reset phone& Erase everything. Before and after.
If your rom doesn't boot try this
http://forum.xda-developers.com/showthread.php?t=1660596
Sent from my U8150 using XDA
Would someone help me? I just installed CM10 Jelly bean for Iconia A500 and flashed the corresponding GApss right after. Now I'm stuck on Acer logo and can't go to recovery. Help.
xmond said:
Would someone help me? I just installed CM10 Jelly bean for Iconia A500 and flashed the corresponding GApss right after. Now I'm stuck on Acer logo and can't go to recovery. Help.
Click to expand...
Click to collapse
Ask here for better assistance
http://forum.xda-developers.com/forumdisplay.php?f=1211
Sent from my U8150 using XDA
Thanks
Allanitomwesh said:
Redownload the rom with a stronger internet connection, flash it again.
Sent from my U8150 using XDA
Click to expand...
Click to collapse
Thanks for your response, I however cannot access my Kindle Fire. It shows up on my computer as 'G:' drive. I can go to TWRP on the device but there's nothing to restore. I think I wiped out everything. There is a message that says "E:failed to mount /sdcard (Invalid argument)" I'm Bricked for good aren't I?
lcharrisej said:
Thanks for your response, I however cannot access my Kindle Fire. It shows up on my computer as 'G:' drive. I can go to TWRP on the device but there's nothing to restore. I think I wiped out everything. There is a message that says "E:failed to mount /sdcard (Invalid argument)" I'm Bricked for good aren't I?
Click to expand...
Click to collapse
Not necessarily, but it does sound like you went abit overboard with clearing data.
Try and restore stock rom on your kindle. The method where you lose root preferably.
Sent from my U8150 using XDA
im very inexperienced.... VERY!...lol well i rooted using the v8 all in one method. fooling around with rom manager, i hit back up current rom while i was downloading one. went to reboot and not past lg screen. tried the power/ vol down recovery and deleting.... would still stop at lg screen. is there any hope? stupid question...... im have a capped plan, so i got stuck while downloading, could it still be downloading? basically pertaining to overages
Reflash Kernel!
Yeah, happened to me once, too!
The problem could be, that you are using a wrong kernel.
Try to reflash the original kernel and the standard rom of your phone and start over again!
And for the next time:
Read the threads CAREFULLY before flashing! This prevents errors and bricking.
Good Luck
The_Mighty_Muffin
the thing is i didnt't "flash" a rom. i just downloaded something within rom manager and it happened while backing up current rom. now how do i go about fixing it. im not really sure how. thanks in advance
please help
All I can tell you is...as long as you can see something, a blinking screen, a logo, anything, there is still hope. Where you using the phone or some PC based software?
i was using the rom manager. i just need help getting this thing stock. dont care about deleting anything. just want it to work, thank you in advance
i think my only problem is getting the vs910.dll to work... dont know what version. i had latest ota update
Everybody out there is asking, how to unbrick this, how to unbrick that? Or if you're in the Evo 3D thread, how do I brick my Evo 3D?
What I'd like to know is, why, or how does a phone get bricked? If you have a USB with corrupted files, you can just totally wipe it and start fresh. If there's no hardware troubles, why isn't there a way to just do a wipe of everything and start fresh?
And also, how is it that a phone gets bricked in the first place? I've heard about things with Emmc boot, getting stuck there, wiping bootloader, etc. But I've flashed multiple different bootloaders, and you have to dabble with Emmc boot while getting S-OFF, so why is it impossible to get out of these if you get stuck in them? Isn't it just software holding you back?
Honestly, if you really just wanted, couldn't you just use an ultra powerful magnet to the NAND Memory to ultra wipe everything? I mean phones aren't assembled with bootloaders or any data in them, in a sense they're factory bricked when they're first created... no?
Ah well, I suppose that's all.
Hungry for information,
TBG
Phones get bricked when you go somewhere in the software that you can't get out of,or you edit the software wrongly, so it doesn't work right anymore. Of course,you could always break something,and kill your phone.
Sent from my U8150 using xda app-developers app
But why is it you can't do a total erase and obliterate every trace of memory from the phone and re-write it? I know the on board memory in a phone doesn't come pre programmed with memory...
thebeastglasser said:
But why is it you can't do a total erase and obliterate every trace of memory from the phone and re-write it? I know the on board memory in a phone doesn't come pre programmed with memory...
Click to expand...
Click to collapse
No but things like the eMMC chip DO come pre-programmed. If you simply wiped every trace of memory from any phone then it would have no idea how to boot up, how to interface to the USB, how to do anything.
Most of the time a 'Bricked' phone is actually caused by someone not reading properly first and not following the instructions correctly, or by thinking they know better than everyone else and can skip a step or take a shortcut.
On the HTC Desire S there was a problem with the eMMC chips 'frying' - normally caused by people who insisted on pulling their batteries after a lock-up and then re-inserting them quickly before the circuitry had discharged fully
The reasons why phones get bricked :
-Because of a nooby brain
-Corrupted ROM that is not Welly built
-Flashing wrong updates, kernels, ROMS...
-Messing up build.prop
.....many numerous other reasons.
You will understand what bricking means only when you brick your beloved phone
That moment is just like a Mini-Heart attack.
Sent from My Premium Calculator HD
No trust me, I semi bricked my old E4G for Sprint as well as my Transformer Prime and was stuck in fastboot with my Evo 3D... trust me, I'm kind of the definition of mini heart attack...
But why can't you get out of a "hard brick?" And what is it that defines a hard brick that makes it so that you can't do anything else?
EDIT: And does abhardbbrock have to be a hardware error? Or can it be a software error?
EDIT2: Although I suppose I already knew it could be a software error... It can happen easily while getting S-OFF on the EVO 3D.
Probably the most obvious case of "hard brick" is when you can't even start the phone, or open the bootloader, which means that there is no way to reverse the situation as you can't get access. Not sure what's the actual reason these things happen though.
thebeastglasser said:
No trust me, I semi bricked my old E4G for Sprint as well as my Transformer Prime and was stuck in fastboot with my Evo 3D... trust me, I'm kind of the definition of mini heart attack...
But why can't you get out of a "hard brick?" And what is it that defines a hard brick that makes it so that you can't do anything else?
Click to expand...
Click to collapse
Most of the time a hard brick is the result of a part of memory getting wiped that you don't have access to flash to e.g emmc chip,if it gets damaged you can't just flash it as its preprogrammed
Sent from my Nexus 7 using xda premium
zacthespack said:
Most of the time a hard brick is the result of a part of memory getting wiped that you don't have access to flash to e.g emmc chip,if it gets damaged you can't just flash it as its preprogrammed
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
ALRIGHT, now that makes sense. Thank you for clarifying. I salute you sir.
Yup, when a device is hard bricked, memory that contains drivers for the boot sequence has been erased or corrupted. Thus, the device quite literally doesn't know how to boot. Data has been erased that can only be manipulated during hardware assembly.
Sent from my iPad using Tapatalk HD
flashing gapps
DD-Ripper said:
The reasons why phones get bricked :
-Because of a nooby brain
-Corrupted ROM that is not Welly built
-Flashing wrong updates, kernels, ROMS...
-Messing up build.prop
.....many numerous other reasons.
You will understand what bricking means only when you brick your beloved phone
That moment is just like a Mini-Heart attack.
Sent from My Premium Calculator HD
Click to expand...
Click to collapse
if im using goo manager and check for updates,, does that automatically show me the updates for my phone {verizon s3} and my rom or are they for every phone???
Micromax a76
i have successfully changed my recovery , then i booted my phone with custom UI from zip file... it worked ... then i made factory reset ... my phone stucked in boot loop ... i tried to get into my recovery mode but its not working , phone is going in default factory mode which is in chineese i translated it but it consist of option of testing hardware only .... what to do? how can i get into recovery mode ? is there a way to install custom recovery via USB ? micromax A76
AbleAmazing said:
Yup, when a device is hard bricked, memory that contains drivers for the boot sequence has been erased or corrupted. Thus, the device quite literally doesn't know how to boot. Data has been erased that can only be manipulated during hardware assembly.
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
it was built and programmed this way, probably so people won't root their phone its a win win cause you don't get to change what you get and if you do and **** this up its your fault and you need to buy a new one(from them) cause who will stay without a phone now days?
Welp, my phone got hard bricked for no reason... I just tried to turn it on, but I get nothing but a LED flash... and that's only if it is charging. My phone is a Moto G, and I have had no problems with it until recently... I can't even get the files to show on my chromebook... I am screwed, aren't I?
So... why can't you just change those little parts to working one that are preprogrammed and why aren't phones made like PC??? You do some s*** with OS... just reinstall it
How to repair soft bricked android?
Okay so first of all I will let you know why a phone gets bricked-
>Corrupted Rom
>Some system files got deleted
>Rooting
>Modding
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
MY CASE
I always keep two phones with me like one for my experiments and one as a backup. In this case I'll be talking about my LYF WIND 3 that got bricked.
>Actually I was trying to install TWRP onto that phone but first I had to root it, and due to the upgraded android security, I wasn't able to do via KingoRoot so I tried I-ROOT and it did the job but instead of kingo-superuser I got some ****ty superuser so i tried granting permission to the actual SUPERUSER and while doing so I accidentally double rooted my phone (First with I-ROOT and then with KingoRoot), which was kinda stupid, so it just deleted some system files and my phone wouldn't boot after that. It just got stuck on the boot logo.
>The second time I was trying to replace the boot animation and logo but did something wrong so the same situation arose again.
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
CURE
So my phone uses a Qualcomm CPU so i just guessed I'll flash it again.
*After Intense Googling*
I found this software QFIL (Qualcomm Flash Image Loader)
I downloaded this file and the drivers for my device. *Google it you'll find for yours too*
Then I downloaded the Stock Rom for my device *Google it again*
Now I just went over to Flat Build in that software and loaded the firehose file and the rawprogram.0 and Patch.0
Now I had just put my device in Download Mode (Volume Keys and Power Key)
Connected via USB and it detected it and then just clicked on DOWNLOAD
It takes about 5 minutes.
After this your phone gets good as new (Unroot, Full Reset)
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
I have a Mediatek device from a local brand (Greentel G9) and now it's stuck in a bootloop and I can't recover from it. I will list all the details below. Any help is deeply appreciated.
*Issue - Stuck in a bootloop. (phone starts up and then the boot animation begins to plays continuously. Another thing that I have noticed is that the boot animation is played in reverse. Not sure why, though. )
*Cause - Attempted Build.prop edit ( I was trying to enable soft keys, but never thought it would be so dangerous)
What I did so far - I have the original Build.prop and a dump of the stock system in .tar format.
As this is an relatively unknown device, no custom recoveries are available, and many attempts to make one myself failed. (this phone also have ubifs partitions,which are not supported by CWM) Have the stock recovery backed up.
Phone currently runs 4.2.2 and is rooted but USB Debugging is disabled.
1). Tried pushing the Build.prop via ADB with the ADB option in stock recovery. Failed! Gives an error 'closed' probably because of disabled USB Debugging.
2). Tried fastboot but it's wasn't helping too. Doesn't have anything to flash.
I'm not really new to Android modding. I previously had an HTC Wildfire, but having CWM made things easier. But I'm still aware of the risks involved.
But now, I'm really stuck. I'm not sure there is anything else I can do. But, I would deeply appreciate any help if recovering the phone is still possible.
Thank you.
Sorry bro... But I think you should find stock firmware.....
Hope this helps
Sent from my GT-S7582 using XDA Premium 4 mobile app
Killwish said:
Sorry bro... But I think you should find stock firmware.....
Hope this helps
Sent from my GT-S7582 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't think it's easy to find firmware for devices like this.
I'm thinking of getting a new phone anyway. So, I give up on recovering this.
Thanks for trying to help.
Cheers...