Related
Hi there Android people.
I am having some issues with running the current Cyanogen *4.2.11.1*.
Phone: G1 Drea100 PVT 32B with stock 1GB SD
using anmon RA 1.5.2 recovery image
-wipe all available in menu.
-created a new partition- FAT32, Ext1 (upgraded to 4), Swap 32MB
-wiped all again.
-repair SD: ext
-flash signed-dream-devphone-userbug-ota-14721
-Once the flash above completed I did not restart, I simply flashed to update-cm-4.2.11.1
-reboot
Once it boots, my home process stops responding if I touch anything. This last for about 15 seconds, after that it seems to responds fine, but the browser and market place seems to auto-close on me from time to time, and I get random phone reboots, after a few reboots my phone simply stops turning on. I have to wait about 10 minutes to get into recovery and try to flash all over again.
I tried fix_permissions in the terminal, no luck.
I did some reading and noticed a lot of people are running different Radio/SPL versions other than stock, I am no super user, so I don't know if any of this effects ROMs, or if I should be flashing either for any sort of benefits I am missing out on? could this be the issue? Current SPL/Radio below:
HSPL10.95.3000
CDLP-4
Radio-2.22.19.261
Any input would be much appreciated.
Thanks,
D3AD PIX3L said:
Hi there Android people.
I am having some issues with running the current Cyanogen *4.2.11.1*.
Phone: G1 Drea100 PVT 32B with stock 1GB SD
using anmon RA 1.5.2 recovery image
-wipe all available in menu.
-created a new partition- FAT32, Ext1 (upgraded to 4), Swap 32MB
-wiped all again.
-repair SD: ext
-flash signed-dream-devphone-userbug-ota-14721
-Once the flash above completed I did not restart, I simply flashed to update-cm-4.2.11.1
-reboot
Once it boots, my home process stops responding if I touch anything. This last for about 15 seconds, after that it seems to responds fine, but the browser and market place seems to auto-close on me from time to time, and I get random phone reboots, after a few reboots my phone simply stops turning on. I have to wait about 10 minutes to get into recovery and try to flash all over again.
I tried fix_permissions in the terminal, no luck.
I did some reading and noticed a lot of people are running different Radio/SPL versions other than stock, I am no super user, so I don't know if any of this effects ROMs, or if I should be flashing either for any sort of benefits I am missing out on? could this be the issue? Current SPL/Radio below:
HSPL10.95.3000
CDLP-4
Radio-2.22.19.261
Any input would be much appreciated.
Thanks,
Click to expand...
Click to collapse
Why did you use "signed-dream-devphone-userbug-ota-14721"
I'm no pro but I used the base image that cyanogen recommends on his wiki page. The DRC83 defanged located here:
http://wiki.cyanogenmod.com/index.php/Latest_version#Defanged_DRC83
staunty said:
Why did you use "signed-dream-devphone-userbug-ota-14721"
I'm no pro but I used the base image that cyanogen recommends on his wiki page. The DRC83 defanged located here:
http://wiki.cyanogenmod.com/index.php/Latest_version#Defanged_DRC83
Click to expand...
Click to collapse
He used that because it is the proper image to use. A defanged file simply means that it has been rendered safe to download with no fear of infection. The link on his site is to the file used by the OP, so no worries there. Also, your radio is good, so do not worry about that either.
I have to ask, because you did not mention part of the process that should be happening. You flash the HTC image, then you do not reboot and flash the CyanogenROM. At this point you reboot. What happens? It should flash the radio, go to an HTC screen, stay for awhile, then reboot itself back to recovery where it gives a message regarding the cache being cleared. At this point you reboot for the actual boot process. Is this not happening for you?
cloverdale said:
He used that because it is the proper image to use. A defanged file simply means that it has been rendered safe to download with no fear of infection. The link on his site is to the file used by the OP, so no worries there. Also, your radio is good, so do not worry about that either.
I have to ask, because you did not mention part of the process that should be happening. You flash the HTC image, then you do not reboot and flash the CyanogenROM. At this point you reboot. What happens? It should flash the radio, go to an HTC screen, stay for awhile, then reboot itself back to recovery where it gives a message regarding the cache being cleared. At this point you reboot for the actual boot process. Is this not happening for you?
Click to expand...
Click to collapse
You are correct- after flashing CM the phone will flash the radio and reboot to the recovery screen where I will reboot again. Sorry for not including that detail.
Home process hanging in the beginning is not a problem, most people have that happenning. Eventhough home screen is shown, Android is still booting up, you just have to wait a little bit for everything to finish up.
Problems with stock apps usually indicate that something went wrong with instalation of the rom (i.e HTC 1.6 rom was not installed properly) so you may want to re-flash that again followed by CM rom of your choice.
Next time you phone reboots itself, try to get a log (there's more on how to do it in Cyan's thread), it's the only way to find out what happens.
Last, but not least, stock 1GB card is not advised for swap/apps2sd because if it's slow speed (it's class 2). Get one that's faster (class 6 preffered) and try that out, it may be the source of your problems after all.
Good luck.
how do i install this Cyanogen on my G1 with 1.6 firmware ?
simple007 said:
how do i install this Cyanogen on my G1 with 1.6 firmware ?
Click to expand...
Click to collapse
http://tinyurl.com/yjuy6u3
But in all seriousness
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
This would work. Please use search, this is such a n00b question.
Did another fresh install, so far no issues.
I will get a log the next time I install to see if I can track down the issue.
Also had time to install Enoch 4.2.11.2 theme. <3 this theme.
I will be heading to Frys today to pick up some cooling fans for the old PC, I will take a look for new mini SD
thank you to everyone that responded.
Just got home from Frys Electronics.
Purchases an A-DATA 8GB Class 6 microSD.
wiping/flashing again.
I am having a hard time learning about the swap file part of all this... I can find guides on how to create a Swap Partition, but not sure how to make it work and/or optimize it.
So I created a 32MB Swap- Previously I read the commands to enable Swap through the terminal- "linux_swap_en=1" I have used this and it does indeed turn on swap, but is there some sort of command to optimize? I believe tweaking the swap files is adjusting the "swappiness"?
The other way I enabled the Swap file was from the spare parts menu- Enabling Compache enabled my Swap file. Does this need adjustment? for size? or any other parameters? Or is this kind of an auto on for Swap?
Sorry I am a total noob, and want to know if I am missing out, I just keep loving this phone more and more.
I will be buying Cyanogen some beer soon ^_^
I've played with swap a long time ago and never quite understood it neither. As of lately, I've been running 10mb hack (in the developement section) and it works great. If you're inclined to get the swap thing going I suggest you read this thread. This will give you an idea of how to enable and tweak swap-related tasks.
Glad to hear that you have original problems taken care of (so far at least).
Good luck.
I think I just may have bricked my phone...
I did all the steps stated in my first post while flashing to 4.2.12.2 and got things going great. Flashed Enoch's Theme 4.2.12.2. Everything was rocking.
Then today, it shut it self off, I rebooted. Got to Enoch load screen then shut off, tried it again, and it won't even get past the G1 splash screen. I have had this happen a few times before, where it would power off randomly and I had to pull the battery, wait like 5 minutes and then get into recovery and clear/flash again. Now I am getting into recovery but after a minute or so it just shuts itself off again.
Can't wipe, Can't flash, cant even get into Cam+power to flash back to previous RC...
Not really sure what to do at this point...
If I do manage to get it running again, I do wonder why its doing this.
I use Cachemate to clear my catche and task killer to kill apps. Could Cachemate be the culprit in this mess, its the only app that I own that uses root? Not sure what else to blame it on other than the G1 one being one big POS and is only good if you can even get a ROM to run on it. I am 5 minutes away from ordering a Nexus.
once again thanks in advance for any input you can provide.
D3AD PIX3L said:
I think I just may have bricked my phone...
I did all the steps stated in my first post while flashing to 4.2.12.2 and got things going great. Flashed Enoch's Theme 4.2.12.2. Everything was rocking.
Then today, it shut it self off, I rebooted. Got to Enoch load screen then shut off, tried it again, and it won't even get past the G1 splash screen. I have had this happen a few times before, where it would power off randomly and I had to pull the battery, wait like 5 minutes and then get into recovery and clear/flash again. Now I am getting into recovery but after a minute or so it just shuts itself off again.
Can't wipe, Can't flash, cant even get into Cam+power to flash back to previous RC...
Not really sure what to do at this point...
If I do manage to get it running again, I do wonder why its doing this.
I use Cachemate to clear my catche and task killer to kill apps. Could Cachemate be the culprit in this mess, its the only app that I own that uses root? Not sure what else to blame it on other than the G1 one being one big POS and is only good if you can even get a ROM to run on it. I am 5 minutes away from ordering a Nexus.
once again thanks in advance for any input you can provide.
Click to expand...
Click to collapse
This sounds like a hardware issue, and not a bricking. Try a new battery, this may fix it, otherwise I am not sure.
cloverdale said:
This sounds like a hardware issue, and not a bricking. Try a new battery, this may fix it, otherwise I am not sure.
Click to expand...
Click to collapse
I will try the other battery I have at home in my other G1 and report back
D3AD PIX3L said:
I will try the other battery I have at home in my other G1 and report back
Click to expand...
Click to collapse
I tried it.
Same issue.
I did noticed that the batter pins were abnormal... One was sticking out more which was normal according to my other G1, the other 2 were shoved down. I tried to mess with the 2 to get them to pop back up to their normal position with no luck.
I am thinking about ordering a replacement.
okay, so tonight I am going to take the G1 apart and see if I can get those pins straightened out. Not sure if it will help, but its better than declaring it a paper weight.
will post the outcome.
Just out of curiousity (and I don't exactly know where I'm going with this) will your phone turn on and stay on if you plug it in (usb or charger)?
borodin1 said:
Just out of curiousity (and I don't exactly know where I'm going with this) will your phone turn on and stay on if you plug it in (usb or charger)?
Click to expand...
Click to collapse
It does not.
I think i will take both phones apart and swap out the screen since that is why I don't use the one. I watched a visual walkthrough seems easy enough
Has anyone disassembled their G1 and reassembled successfully? any tips?
Started to take apart the non-cracked bricked G1.
Once I removed the motherboard and started on the next step, I realized how bad it would be to end up getting the parts swapped and then have it not work... Put it back together and loaded up the latest Cyanogen on my working cracked G1.
*shrugs* it will do for now.
Waiting till the end of next month to order my Nexus 1, then I will have fun ripping apart both G1's and hopefully end up with one great looking, fully functional G1 to possibly sell or keep as an extra phone...
thanks to all who replied!
Ok, so i've spent a few hours at this already but let me give as much info as I can. I have read through many threads searching for info. I am no expert but I have had OG Droid, Incredible, and currently Thunderbolt all rooted so I am a novice.
This is my GFs phone and was previously bone stock, never rooted, no Roms nothing. So she gets the update recently and clicks yes and that is where the trouble began, phone constantly reboots and will not go past the language/activation screen. It never once went past that first screen, and she tried the hard reset and the battery pull.
So this is where I took over. I retried the hard reset (power + vol down) and also the battery pull. I also tried to activate in numerous other languages, all cause a reboot.
As per
http://forum.xda-developers.com/archive/index.php/t-1208713.html
I was finally able to get past the activation screen and make some progress. However after about a minute the phone always reboots, no matter what it is doing. I hard reset in the settings menu and that did nothing.
I next followed
http://forum.xda-developers.com/showthread.php?t=1326347
and got the phone rooted.
Installed
http://forum.xda-developers.com/showthread.php?t=1144951
and than installed CWR 4.0.0.4 ? (not sure the version whatever it comes with) Tested recovery and it it seems to stick even after rebooting several times, which the phone automatically does (maybe its a feature and not a flaw?) So I was unsure of what version of Android was even running because the phone will not allow me to go into about phone it always force closes *com.android.settings* but I figure what the heck and try my luck with a new Rom. I decided on
http://forum.xda-developers.com/showthread.php?t=1326542&page=11
So I did the usual. Rebooted into recovery, made a nandroid backup, wiped data, cache, davlik and even did /system for good measure. Than did the install and upon first boot all the same problems are there. It will not activate from the screen, it just reboots the phone eventually. I used the same method above to avoid the screen and now it will boot up and the phone is in fact running an AOSP Rom but it still reboots after about a minute. Oddly enough it also continues to refuse to let me open About Phone, in the settings menu. I also for good measure went into recovery and wiped everything again and also tried fixing permissions in recovery, all to no avail.
At this point I am thinking it is perhaps just a hardware issue, although the phone does not reboot itself in recovery. I would be willing to try a different Rom, however I don't think it would work. I am wondering if anyone has any other suggestions? Should I try this?
http://forum.xda-developers.com/showthread.php?t=1120062
Other info:
What does work is wifi, so i can get on the internet briefly. I can connect to google and get apps from the market.
I am leaving this for a few hours or I may have to re-title the thread "How do you put the LG Revolution back together after throwing it against a wall?"
Currently I'm sad face that you rooted and installed cwm but I think the update bricked it personally. Hopefully S.Meezy will see this as he has stock recovery. I would say just get back to bone stock and get it replaced. If anyone else knows how to get it fixed, my best guesses would be mt or S.Meezy, though adb that might work. I hope it all gets figured out. Someone needs to post stock GB without data or anything for people to flash to if need be. That might fix your issue.
My suggestion is to get the recover the whole phone...
http://forum.xda-developers.com/showthread.php?t=1211295
follow that but use the v6 TOT file. That will revert the phone to out of factory new, with updated radios. If you still have the issue then I would contact Verizon.
If everything works then you can re-run the update to Gingerbread.
Could be a long shot but I remember seeing something a little way back in another forum where a user w the same problem accidentially resolved his issue by restarting w the sd card out. For him it turned out to be a bad or incompatible sd card at the root of the problem.
If you have one in, pull it and restart. Hope thats it for you...
Sent from my VS910 4G using XDA App
Well i'm a glutton for punishment so i'm back.
I didn't want to bother with rooting it honestly but I did it out of desperation, figured a total wipe + brand new Rom would surely fix things.
Going to attempt the full recovery.
Tried pulling the SD card, than just the Sim card and finally without anything and none of the combinations worked.
Have you tried downloading a stock ROM to your PC/Mac and dropping that on your SD card and then flashing that ROM, after checking the md5? To me it sounds like your gf just had a bad download.
I think the issue is that you keep trying to flash the bad bits. Just my two cents...
Sent from my Dell Streak 7 using Tapatalk
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Haxcid said:
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Click to expand...
Click to collapse
What he said.
Remember: Absolutely do not, under any circumstance, unplug/turn off your phone once you start that process. It can take awhile, and might look like it froze, but just let it do it's thang.
I had a problem a few days ago that i was having problems after rooting my phone so i brought it back to stock using RSD Lite and then tried to flash a new rom on the phone and it said my phone was not unlocked so i downloaded The Myth Tools and unlocked it that way but I am wondering if i messed it up because i did not really know what i was doing i just tried to see if i could figure it out and it seemed like it worked until today. I flashed Touchwiz on there a couple days ago and it worked fine i made a backup wiped the cache,dalvik cache and system now today it randomly freezes and is now stuck on the bootloader unlocked screen. I can hold down power and volume up and boot into recovery which is ClockworkMod Recovery v6.0.3.6 touch and it also says under that in the bottom right of the screen Warning No file_contexts now i dont know if it has always said that since i flashed this recovery or just started. I also once again tried wiping the cache and dalvik cache because i read it on another post of someone stuck on this screen so i tried that and rebooted it still the same result stuck on bootloader screen. At this point i have no idea what to do. If i have to start over from stock because i messed up unlocking it or completely wipe it again and reflash touchwiz or another rom. I have had nothing but problems since rooting this phone I have gone through atleast 6 to 8 roms because every single one of them gives me a problem somehow. The most common is when i make a call or recieve one and i put the phone up to my ear I know the sensor turns off the screen but when i take it away to end it or do something its completely off or apps force closing all the time still after i did the stock reflash. I am starting to wonder if its just my phone because everyone else i read about has no problems with there phones mine nothing but problems. Please if someone could help me or walk me through this process it would be greatly appreciated I love the things it can do with custom roms but i just wish it would run smooth.
bpc87 said:
I had a problem a few days ago that i was having problems after rooting my phone so i brought it back to stock using RSD Lite and then tried to flash a new rom on the phone and it said my phone was not unlocked so i downloaded The Myth Tools and unlocked it that way but I am wondering if i messed it up because i did not really know what i was doing i just tried to see if i could figure it out and it seemed like it worked until today. I flashed Touchwiz on there a couple days ago and it worked fine i made a backup wiped the cache,dalvik cache and system now today it randomly freezes and is now stuck on the bootloader unlocked screen. I can hold down power and volume up and boot into recovery which is ClockworkMod Recovery v6.0.3.6 touch and it also says under that in the bottom right of the screen Warning No file_contexts now i dont know if it has always said that since i flashed this recovery or just started. I also once again tried wiping the cache and dalvik cache because i read it on another post of someone stuck on this screen so i tried that and rebooted it still the same result stuck on bootloader screen. At this point i have no idea what to do. If i have to start over from stock because i messed up unlocking it or completely wipe it again and reflash touchwiz or another rom. I have had nothing but problems since rooting this phone I have gone through atleast 6 to 8 roms because every single one of them gives me a problem somehow. The most common is when i make a call or recieve one and i put the phone up to my ear I know the sensor turns off the screen but when i take it away to end it or do something its completely off or apps force closing all the time still after i did the stock reflash. I am starting to wonder if its just my phone because everyone else i read about has no problems with there phones mine nothing but problems. Please if someone could help me or walk me through this process it would be greatly appreciated I love the things it can do with custom roms but i just wish it would run smooth.
Click to expand...
Click to collapse
You can enter Recovery, right? What happens if you install a .zip? Right now your phone is stuck in the Motorola logo?
it wouldnt even go to the motorola symbol it just stayed in the first screen where it said your bootloader was unlocked. It would go into recovery and i tried to reboot it and it gave me the same screen. So i wiped it completely cache, dalvik cache and system and shut it off. Last night i plugged it into my comp to put it back to stock and it started up like normal and booted into a rom like i just installed one where you have to fill in all that info and setup wifi if you choose too which was weird because it wouldnt do anything before. Anyways i used RSD Lite and put it back to stock and thats where it is now. I am reading the Atrix HD Beginners Guide written by skeevydude right now and I am thinking about trying to root it again with the help of that article and maybe I will have better luck doing it that way hopefully haha maybe I can finally get a rom to run the way everyone else says they run smooth and fast. Any input though to help me would be much appreciated i am definitely new at this and want to learn its something that interests me alot ever since a friend rooted my phone the first time i cant stop playing with it I was trying to make it as fast as I can I had ProBam on there i think its called ive had touchwiz, motoblur, carbon, liquidsmooth, MIUI, and a couple others I cant remember also had a custom kernel i flashed on there and Pure performance so as you can see I have been trying everything.
bpc87 said:
it wouldnt even go to the motorola symbol it just stayed in the first screen where it said your bootloader was unlocked. It would go into recovery and i tried to reboot it and it gave me the same screen. So i wiped it completely cache, dalvik cache and system and shut it off. Last night i plugged it into my comp to put it back to stock and it started up like normal and booted into a rom like i just installed one where you have to fill in all that info and setup wifi if you choose too which was weird because it wouldnt do anything before. Anyways i used RSD Lite and put it back to stock and thats where it is now. I am reading the Atrix HD Beginners Guide written by skeevydude right now and I am thinking about trying to root it again with the help of that article and maybe I will have better luck doing it that way hopefully haha maybe I can finally get a rom to run the way everyone else says they run smooth and fast. Any input though to help me would be much appreciated i am definitely new at this and want to learn its something that interests me alot ever since a friend rooted my phone the first time i cant stop playing with it I was trying to make it as fast as I can I had ProBam on there i think its called ive had touchwiz, motoblur, carbon, liquidsmooth, MIUI, and a couple others I cant remember also had a custom kernel i flashed on there and Pure performance so as you can see I have been trying everything.
Click to expand...
Click to collapse
Good to know that is working now. I would recommend you to take it easy. Don't flash it everyday, use and know a ROM, then you can decice which one is better for you. Be sure to have a backup if something fails, also save a .zip (ROM) in the SD card. Just FYI, I haven't come across a ROM that is 100% smooth (Not even HoloBlur). They are very good, but maybe not the smooth level that you think.
Hey bpc87, I was wondering if you were able to get a custom ROM up & running after all that & if so, how?
I've had the same issue whenever I tried installing a ROM. It would install & boot okay the first time, but when rebooting, it would get stuck at the "bootloader unlocked" warning screen. I went back to stock using Myth Tools & now, after installing a ROM, a reboot leaves me stuck at the "Motorola Dual Core" screen.
Any help from you & the community would be awesome!
bsmitty said:
Hey bpc87, I was wondering if you were able to get a custom ROM up & running after all that & if so, how?
I've had the same issue whenever I tried installing a ROM. It would install & boot okay the first time, but when rebooting, it would get stuck at the "bootloader unlocked" warning screen. I went back to stock using Myth Tools & now, after installing a ROM, a reboot leaves me stuck at the "Motorola Dual Core" screen.
Any help from you & the community would be awesome!
Click to expand...
Click to collapse
dude i havent even tried to since i flashed it back to stock because i dont want the same thing to happen. The last time I just went to turn on bluetooth and it just rebooted on its own. Not too mention the other problems I had I am not going to mess with it again until I read more on how to root it because it is either that or my phone.
Yeah, I understand. Hopefully then some other users who run into the same problem will investigate & figure out what's goin on. I've seen several other threads of people who've encountered the same thing but unfortunately no answer. For me, this is the determining factor as to whether I end up keeping the AHD or not.
Thanks
I have the same problem. Everytime in moto logo after rebooting, but with stock firmware all ok. Is there any solution for this problem?
Gave my old LG Revo to a buddy, things POS, but its all he has at the moment. Anyways, I had a version of Ginger-volt rom on there, and it was acting up, so I was just gonna update everything and put the last version that came out on it, or go with whatever the newest most stable rom is....So I booted into CWM and did a nandroid back up, then wiped everything, cache, dalvik, etc etc, booted up fine, went through some stuff, then i went back to restore the back up i just made cause he forgot to tell me about some game data he wanted backed up.....
So anyways, i restored it, wiped the cache, then rebooted, and yea, then it went into boot loop, at first it was between the LG Logo and the Boot Animation, but now it just suts at the LG Logo for quite awhile, like 10min, and then restarts, and does it over and over. And I try and hold down Power and Vol-Down, but it doesn't work, can't get into recovery. So Need some help here. I've tried all the old tricks I remember from my LG Revo days, but nothing has worked thus far. Is there a way to like boot into something like ODIN and just flash the Stock Firmware. Like RSD-Lite maybe ? Can't remember if that was Moto only....Think it may have been lol
remembered about the exitrecover.zip thing did that, put sdcard back in phone, booted, holding down power and vol-dwn, and it worked, flashed the .zip and then rebooted, now its doing it once again. WTF. I want this thing back to Stock, and then I am gonna root it and flash a new rom. but before that obviously i need to fix this first. Can someone help me at all. I know there isn't a lot of people left on this forum.
BackSeatSuicide said:
Gave my old LG Revo to a buddy, things POS, but its all he has at the moment. Anyways, I had a version of Ginger-volt rom on there, and it was acting up, so I was just gonna update everything and put the last version that came out on it, or go with whatever the newest most stable rom is....So I booted into CWM and did a nandroid back up, then wiped everything, cache, dalvik, etc etc, booted up fine, went through some stuff, then i went back to restore the back up i just made cause he forgot to tell me about some game data he wanted backed up.....
So anyways, i restored it, wiped the cache, then rebooted, and yea, then it went into boot loop, at first it was between the LG Logo and the Boot Animation, but now it just suts at the LG Logo for quite awhile, like 10min, and then restarts, and does it over and over. And I try and hold down Power and Vol-Down, but it doesn't work, can't get into recovery. So Need some help here. I've tried all the old tricks I remember from my LG Revo days, but nothing has worked thus far. Is there a way to like boot into something like ODIN and just flash the Stock Firmware. Like RSD-Lite maybe ? Can't remember if that was Moto only....Think it may have been lol
Click to expand...
Click to collapse
Try the LG restore tool i think its LGPSNT or something like that, but you need a .TOT, and the you can reroot, flash a recovery, and install an updated ROM, gingervolt is OLD
betatest3 said:
Try the LG restore tool i think its LGPSNT or something like that, but you need a .TOT, and the you can reroot, flash a recovery, and install an updated ROM, gingervolt is OLD
Click to expand...
Click to collapse
well i fixed that stuff on my own, couldn't get anyone to respond so I just went based on what I remember, like i said, it's been awhile since i used that phone
BUT NOW ! I got a whole other issue, and its a lot more F'd up, and I have never dealt with this before, so I am just wingin it on what i've tried so far. But i've hit a wall. So after restoring everything and getting Broke-Out rom back on there and everything, I noticed after a lil bit that it had the No Sim-Card icon in the status bar, and couldn't make a call. Then it hit me, and i didnt wnna say it outloud just in case i was wrong, so looked at About Phone>Status, and yep, Completely zero'd out, IMEI/MEID etc etc. I have no idea what to do. I tried following that guide on here but that program DFS or whatever, I entered my IMEI number in this program and hit "Write" and now its in my phone, so i know its communicating with my phone, but that still didnt fix it, I am missing the HEX number, and where it is located on the phone behind the battery, has been complketely rubbed away, so i cant read it. I don't know if Verizon will tell me what the number is, and I didnt wanna call them cause what am I supposed to tell them, not that we care about the warranty on this phone cause its pretty much on its last legs anyways, but i dont wanna cause any problems on my account, cause I know verizon is pretty anti-custom development,
So any ideas on what to do ?
Anyone ? Any suggestion on how to go about fixing this ?
Hi guys, this is my first post here, so please forgive any mistakes, but I am currently in full freak out mode.
So I am brand new to rooting in general, and I wanted to give it a shot because I have heard so much about it recently with Paranoid Android and battery saving tips. So today I gave it a shot. I actually succeeded, which was pretty neat. I loaded TWRP, and loaded SuperSU. I was pretty glad with what I had done, loaded some root apps. I wanted to install a ROM next, so the first thing I was told was to make a backup, then reset. So I did exactly that. I backed up my ROM using TWRP, then reset. However, it automatically booted itself right back, to which I was greeted with a freshly wiped HTC M7. I was pretty frustrated, so I went back to TWRP and loaded my backup, however, when I did that, it simply got stuck on the "HTC Quietly Brilliant" screen. I have wiped it multiple times, I have done a cache wipe, a full wipe, and reloaded my backup again, and every time I do this I simply am greeted with the same screen, that stays there. I am freaking out because I voided my warranty by unlocking the bootloader, and now I think I bricked my phone. I am still another 6 months out from completing my contract with Sprint, and the only backup phones i have are from the mid 2000s that are clamshell. What can I do to fix this? Is it a brick to begin with? Please help. Thanks.
Edit: I fixed it! I had to go back in, and push a rom so it could load. After I did that, it worked great with the new rom. I guess once you commit you just have to follow through!